git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 13, 2013, 16:55 UTC
Message-ID
<7va9muvtkj.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALkWK0=o0OxTjim=+qoBhpHkWQoVWLWjkJPqknPbr29T5ax46Q@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 10 quoted lines
> Ramkumar Ramachandra wrote:
>> 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?
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 11 of 12 in “Fix git checkout - (early preview)”
  1. 0/3 Fix git checkout - (early preview)Ramkumar Ramachandra, Jun 10, 2013
  2. 1/3 t/checkout-last: checkout - doesn't work after rebase -iRamkumar Ramachandra, Jun 10, 2013
  3. Junio C HamanoJun 10, 2013
  4. Ramkumar RamachandraJun 13, 2013
  5. 2/3 checkout: respect GIT_REFLOG_ACTIONRamkumar Ramachandra, Jun 10, 2013
  6. Junio C HamanoJun 10, 2013
  7. 3/3 rebase -i: write better reflog messages for startRamkumar Ramachandra, Jun 10, 2013
  8. Junio C HamanoJun 10, 2013
  9. Ramkumar RamachandraJun 10, 2013
  10. Ramkumar RamachandraJun 13, 2013
  11. Junio C HamanoJun 13, 2013
  12. Ramkumar RamachandraJun 13, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.