| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-12-03 | Fix typos in changelog | Jonas Bernoulli | |
| 2024-08-18 | Remove "It's Magit!" section from relnotes | Jonas Bernoulli | |
| 2024-08-11 | relnotes: Fix date in url | Jonas Bernoulli | |
| The release was indeed tagged on the 8th, but the announcement wasn't ready until the 9th. | |||
| 2024-08-08 | Release version 4.0.0v4.0.0 | Jonas Bernoulli | |
| 2024-08-05 | Update release notes | Jonas Bernoulli | |
| 2024-08-04 | magit-diff-working-tree: Change diff type to committed | Kyle Meyer | |
| magit-diff-range with a single revision and magit-diff-working-tree both show a diff between the revision and the working tree. Whether magit-reverse aborted in these buffers used to be determined by whether the specified revision resolved to HEAD. If so, magit-reverse aborted with "Cannot reverse unstaged changes". magit-reverse aborting here wasn't entirely right because a diff of HEAD versus the working tree may contain staged changes too. e94b6ebf (Record diff-type in magit-diff-mode buffers, 2023-03-18) moved magit-diff-range and magit-diff-working-tree in different directions. With that change, magit-diff-range with any revision, including HEAD, allows reversing. On the other hand, magit-diff-working-tree with any revision forbids reversing. Update magit-diff-working-tree to pass `committed' instead of `unstaged' for the diff type. As a description, `committed' is a bit off (the diff can include a mix of unstaged, staged, and committed changes), but it allows reversing and matches what magit-diff-range does. For a diff of any revision against the working tree, magit-apply is bound to fail. Before e94b6ebf, magit-apply used to abort when the diff was between _HEAD_ and the working tree. After e94b6ebf and this change, magit-apply leaves the failure to git-apply. To abort early, we could mark working tree diffs with a distinct diff type, but leaving the failure to apply time is good enough, at least for now. Closes #5090. | |||
| 2024-07-24 | relnotes: Fix typo | Kyle Meyer | |
| 2024-07-24 | Copy edit release notes | Jonas Bernoulli | |
| 2024-04-02 | Update release notes | Jonas Bernoulli | |
| 2024-04-01 | Move misplaced release note entry | Jonas Bernoulli | |
| 2023-12-29 | magit-bisect-run: Restore checks for flipped revs and dirty tree | Kyle Meyer | |
| As of Magit v2.90.0, magit-bisect-start aborts if the revisions are flipped or there are uncommitted changes. magit-bisect-run shared those guards at the time because it used magit-bisect-start underneath, but f592e367 (magit-bisect-run: Don't start bisect asynchronously, 2021-06-20) moved away from magit-bisect-start, unintentionally losing the checks. Restore the checks by extracting them to a shared helper. Closes #5070. | |||
| 2023-10-23 | magit-insert-am-sequence: Account for already applied patches | Kyle Meyer | |
| magit-insert-am-sequence inserts a section for all patches in $GIT_DIR/rebase-apply/ and then displays ORIG_HEAD through HEAD via magit-sequence-insert-sequence. If the 'git am' call fails to apply a patch, this leads to repeated sections for successfully applied patches because Git leaves the patch files around after successfully applying a patch. Avoid the repeated sections by explicitly inserting a section only for $GIT_DIR/rebase-apply/ patches that have not been applied, leaving the rest to the magit-sequence-insert-sequence call. Closes #5024. | |||
| 2023-02-06 | Next release will be named 4.0.0 | Jonas Bernoulli | |
 |
index : magit.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| aboutsummaryrefslogtreecommitdiff |