Re: [PATCH 3/3] rebase -i: write better reflog messages for start

Ramkumar Ramachandra [off-list ref] writes:

Ramkumar Ramachandra wrote:

quoted

t/status-help.  Looks seriously unrelated, and I'm breaking my head
over it.  Any clues?

Damn it!  A recent commit is responsible for this avalanche in test
breakages: b397ea (status: show more info than "currently not on any
branch", 2013-03-13).  It re-implements a backward version of
grab_nth_branch_switch(): grab_1st_switch() essentially _relies_ on
the random unintended pollution that rebase writes to the reflog to
print a more useful (?) status :/

After "git checkout v1.3.0", it is reasonable to expect that you can
tell what you checked out and what state you are in.  If you then
made a few commits or resetted to some other commit, it is debatable
if "detached from v1.3.0" is useful or the subtle difference between
"detached at" vs "detached from" is confusing.

But what does it have to do with rebase polluting the reflog?

Junio C Hamano wrote:

But what does it have to do with rebase polluting the reflog?

See the series I just posted.