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

Re: [PATCH] Make rebase save ORIG_HEAD if using current branch

From
Johannes Sixt <j.sixt@viscovery.net>
Date
May 7, 2008, 08:14 UTC
Message-ID
<482164F6.4010205@viscovery.net>
In-Reply-To
<54536F65-3A06-482E-9806-2E4F643C1024@silverinsanity.com>
Brian Gernhardt schrieb:
Show 11 quoted lines
> On May 6, 2008, at 2:32 AM, Johannes Sixt wrote:
>> Brian Gernhardt schrieb:
>>> +    echo "$branch" > "$GIT_DIR/ORIG_HEAD"
>>
>> 1. You should be using 'git update-ref' here, I think.
>> 2. You should detect errors.
> 
> This is exactly how git-merge.sh does it.  While that's not a good
> argument for adding this, perhaps merge should be updated as well.  And
> presumably update-ref will make detecting errors easy.  But is being
> unable to set ORIG_HEAD an error that should stop the entire process?
Probably not.
Show 11 quoted lines
>> 3. Should ORIG_HEAD better be set at the end of the rebase, not at the
>> beginning? Because if the rebase stops for some reason, and then you do a
>> 'git reset', you'll have overwritten the ORIG_HEAD that you have set
>> here.
> 
> I put it where I did because I thought it would only make sense when
> rebasing the current HEAD (instead of the two argument version that
> switches first).  Duplicating the logic to determine that later seemed
> wasteful.  Also, might you want to access the original HEAD during a
> rebase conflict?  (Although that would argue that ORIG_HEAD should be
> set for all rebases, to $upstream.)

Well, I can't think of a use-case where ORIG_HEAD would be extremly useful for _me_, but you argued for one (git pull --rebase), so you make it so that it suits you. I'm just drawing a scenario where ORIG_HEAD possibly is not what you expect.

-- Hannes
Previous: Brian GernhardtNext: Junio C Hamano
Message 4 of 5 in “Make rebase save ORIG_HEAD if using current branch”
  1. Make rebase save ORIG_HEAD if using current branchBrian Gernhardt, May 6, 2008
  2. Johannes SixtMay 6, 2008
  3. Brian GernhardtMay 6, 2008
  4. Johannes SixtMay 7, 2008
  5. Junio C HamanoMay 7, 2008

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.