1. 14 Jul, 2018 2 commits
  2. 12 Jun, 2018 1 commit
    • Miciah Masters's avatar
      Fix magit-commit-add-log with commit.verbose=true · 52059dca
      Miciah Masters authored
      When Git was configured with commit.verbose=true, magit-commit-add-log
      would append lines after the diff, past the cut line.  It should avoid
      appending lines after the first comment.
      
      * lisp/magit-commit.el (magit-commit-add-log-insert): Narrow the region
      to include everything up to the first comment.
      52059dca
  3. 10 Jun, 2018 1 commit
  4. 07 Jun, 2018 2 commits
  5. 12 May, 2018 3 commits
  6. 20 Apr, 2018 1 commit
  7. 02 Mar, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 07 Jan, 2018 1 commit
  10. 05 Nov, 2017 1 commit
    • Jonas Bernoulli's avatar
      magit-commit-diff: never give up · d25fb656
      Jonas Bernoulli authored
      Fallback to the same base logic as `magit-diff-while-committing' to
      decide what diff to display instead of giving up when we don't know
      what diff to display based on `last-command'.
      
      We cannot use that function, because if we did then we might end up
      toggling to the "other diff" if the diff buffer already exists.
      
      The "unrecord" and "abort" logic have be moved to the "outside".
      d25fb656
  11. 23 Oct, 2017 1 commit
  12. 11 Oct, 2017 4 commits
  13. 07 Oct, 2017 3 commits
  14. 09 Aug, 2017 1 commit
  15. 11 Jul, 2017 1 commit
    • Kyle Meyer's avatar
      magit-commit-popup: add custom reader for --reuse-message · 9eb60c0c
      Kyle Meyer authored
      As mentioned in git-reset's manpage, ORIG_HEAD can be useful for
      undoing a commit and reusing its message (though there are of course
      other ways to do this).  Define a reader for the --reuse-message
      option that offers ORIG_HEAD as the default value when it exists.
      
      Also, prompt with all ref names.  If these aren't useful for the given
      situation, the user can ignore them and enter an arbitrary value.
      
      Closes #3110.
      9eb60c0c
  16. 10 Jun, 2017 1 commit
  17. 12 Mar, 2017 1 commit
  18. 05 Feb, 2017 1 commit
  19. 19 Jan, 2017 1 commit
    • Jonas Bernoulli's avatar
      While committing, diff from inside gitdir if necessary · 9e0e2a24
      Jonas Bernoulli authored
      If a repository is created using `git init --separate-git-dir', then
      that does not set `core.worktree' (unlike what `git submodule' does).
      
      When committing inside such a repository `magit-commit-diff' is run
      inside the gitdir, and there is no way to prevent that.  Luckily `git
      diff' also works inside the gitdir, but because many other commands
      don't, we always run everything in the working tree.
      
      This is fairly deeply ingrained, so we have to add a kludge to
      `magit-toplevel', that causes it to return the gitdir instead,
      and that is triggered by dynamically binding the new variable
      `magit-toplevel--force-fallback-to-gitdir' to a non-nil value.
      
      And `magit-commit-diff' now does so to fix #2955.
      9e0e2a24
  20. 04 Jan, 2017 1 commit
  21. 29 Dec, 2016 3 commits
  22. 27 Dec, 2016 1 commit
  23. 22 Dec, 2016 1 commit
    • Jonas Bernoulli's avatar
      Place magit-{*}-arguments in new magit-git-arguments group · 33c5c1ca
      Jonas Bernoulli authored
      Most options named `magit-TOPIC-arguments' specify the arguments
      that are enabled by default in the respective `magit-TOPIC-popup'.
      Previously most of these options were placed in the `magit-commands'
      Custom group, which made that group rather noisy.  A few were placed
      in others group, which was inconsistent and in most cases an oversight.
      
      To avoid having to specify the group for each and every popup defined
      in Magit and in third-party extensions that share the "magit-" prefix,
      teach `magit-define-popup' to use `magit-git-arguments' if GROUP isn't
      specified and NAME does begin with "magit-".
      
      Also place `magit-git-global-arguments' into this group.  Remove it
      from `magit', but keep it in `magit-process' as before.
      33c5c1ca
  24. 20 Nov, 2016 1 commit
  25. 08 Oct, 2016 1 commit
  26. 24 Sep, 2016 1 commit
  27. 07 Sep, 2016 1 commit
  28. 11 May, 2016 1 commit
    • Jonas Bernoulli's avatar
      magit-commit-diff: make sure diff buffer doesn't replace message buffer · c1e0de86
      Jonas Bernoulli authored
      When the window that just began displaying the commit buffer previously
      displayed the diff buffer, then displaying that buffer again would
      likely be done by displayed in that same window, causing the commit
      message buffer would no longer be displayed anywhere.  Prevent that by
      removing the diff buffer from the window's list of previously displayed
      buffers.
      
      Also remove the kludge in `magit-display-buffer-traditionally', which
      was also supposed to deal with this issue.
      c1e0de86
  29. 21 Apr, 2016 1 commit
    • Jonas Bernoulli's avatar
      magit-commit-squash-internal: commit synchronously before rebase · f6601b3c
      Jonas Bernoulli authored
      Previously it was possible for the commit process to still hold the lock
      on index.lock, when the rebase process was trying to acquire it.  Now we
      run the commit process synchronously if we are going to also rebase, and
      we also forgo refreshing between the two processes.  If we don't rebase,
      then still commit asynchronously and refresh.
      f6601b3c