All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Haller <lists@haller-berlin.de>
Cc: git@vger.kernel.org
Subject: Re: When exactly should REBASE_HEAD exist?
Date: Wed, 08 Mar 2023 11:40:54 -0800	[thread overview]
Message-ID: <xmqqa60nt4jd.fsf@gitster.g> (raw)
In-Reply-To: <28b78355-e3db-d33a-c576-653740a4a1f3@haller-berlin.de> (Stefan Haller's message of "Wed, 8 Mar 2023 20:02:26 +0100")

Stefan Haller <lists@haller-berlin.de> writes:

> On 07.03.23 19:07, Junio C Hamano wrote:
> ...
>> Stepping a bit, how does our "git status" fare here?  It shows what
>> step in a sequence "rebase -i" the user who got control back (due to
>> "break", "exec sh", "edit" or a conflicted "pick") is in.  Or at
>> least it tries to.  Does it suffer from the same "great, but ..."?
>> ...
>
> It fares a little better, but not much, and it doesn't look like I can
> use its information to implement the behavior I want.

Thanks.  That is the kind of information I was trying to find.  It
means that the current "git status" does not give our users enough
clue as to where in their "rebase -i" session they are at, and we
will help more users by teaching "git status" the trick you are
designing.  Instead of peeking into how the implementation details
like REBASE_HEAD currently happen to work, making sure underlying
"git" knows how to present the information you want and letting it
perform the heavy lifting would make sure the solution will stay
supported across versions of future git.




  reply	other threads:[~2023-03-08 19:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 12:55 When exactly should REBASE_HEAD exist? Stefan Haller
2023-03-02 10:19 ` Phillip Wood
2023-03-02 20:27   ` Stefan Haller
2023-03-03 10:57     ` Stefan Haller
2023-03-03 21:25       ` Chris Torek
2023-03-04  8:36         ` Stefan Haller
2023-03-06  3:31           ` Chris Torek
2023-03-07 13:16             ` Stefan Haller
2023-03-05 14:33       ` Phillip Wood
2023-03-05 16:58         ` Stefan Haller
2023-03-05 14:31     ` Phillip Wood
2023-03-05 16:59       ` Stefan Haller
2023-03-05 19:13         ` Stefan Haller
2023-03-05 20:15           ` Phillip Wood
2023-03-08 19:02             ` Stefan Haller
2023-03-10  9:56               ` Phillip Wood
2023-03-10 17:42                 ` Stefan Haller
2023-03-16 17:46                   ` Phillip Wood
2023-03-19 14:50                     ` Phillip Wood
2023-03-20  7:29                       ` Stefan Haller
2023-03-20  8:42                         ` Stefan Haller
2023-03-07 18:07 ` Junio C Hamano
2023-03-08 19:02   ` Stefan Haller
2023-03-08 19:40     ` Junio C Hamano [this message]
2023-03-09 14:45       ` Stefan Haller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqa60nt4jd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lists@haller-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.