Your message dated Tue, 19 Jun 2018 18:59:18 -0700
with message-id <[email protected]>
and subject line Re: want <reason> option to git-rebase
has caused the Debian Bug report #901805,
regarding git rebase: allow calling scripts to customize reflog action
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
901805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901805
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git
Version: 1:2.11.0-3+deb9u2
git-rebase leaves entries like this in the reflog:
c15f4d5391 HEAD@{33}: rebase: checkout
c15f4d5391ff07a718431aca68a73e672fe8870e
It would be nice if there were an option to control this message.
Particularly, when another tool invokes git-rebase, the other tool may
specify an interesting --onto, and there is no way to record any
information about that --onto commit.
git-rebase already has a -m option, so I suggest
--reason=<reason>
It doesn't matter much exactly how the provided string is used.
Any of the following would be good IMO:
<reason>
rebase start: <reason>
I think:
rebase: checkout c15f4d5391ff07a718431aca68a73e672fe8870e <reason>
would be rather cumbersome.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
notfound 901805 git/1:2.11.0-3+deb9u2
quit
Hi again,
Ian Jackson wrote:
> git-rebase leaves entries like this in the reflog:
>
> c15f4d5391 HEAD@{33}: rebase: checkout
> c15f4d5391ff07a718431aca68a73e672fe8870e
>
> It would be nice if there were an option to control this message.
Thanks for a clear report. As described upstream[*], you can do this
using the GIT_REFLOG_ACTION environment variable. See the ENVIRONMENT
VARIABLES section in git(1) for more details. This mechanism was
introduced around v1.8.4.
I'm happy to improve the documentation or behavior of that mechanism
to better fit your needs.
Sincerely,
Jonathan
[*] https://public-inbox.org/git/[email protected]/
--- End Message ---
