From: Catalin Marinas <catalin.marinas@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: use of temporary refs in resolve
Date: Mon, 08 Aug 2005 09:50:30 +0100 [thread overview]
Message-ID: <tnxk6iwx161.fsf@arm.com> (raw)
In-Reply-To: <7v3bplwmzg.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 07 Aug 2005 12:44:35 -0700")
Junio C Hamano <junkio@cox.net> wrote:
> Here is my understanding of various "temporary heads" left
> directly underneath $GIT_DIR:
>
> HEAD : updated only after successful auto merge.
>
> ORIG_HEAD : records the head value before resolve started.
> if automerge fails, this is the same as HEAD,
> but after successful automerge, this can be used
> to see what the previous head was. This is the
> first parent of the resulting commit.
>
> MERGE_HEAD: present if auto merge is unsuccessful and
> records the other head being merged.
>
> LAST_MERGE: present if merge is unsuccessful or impossible and
> records the other head being merged.
Is FETCH_HEAD going to be preserved by the git-fetch-script operation?
It should be, unless, git-pull-script removes it or it is changed to
do the fetch as well.
In a repository managed with StGIT (i.e. updated with 'stg pull'), the
base of the stack is always the same with FETCH_HEAD and StGIT uses
this file. I also find it quite useful for:
gitk ORIG_HEAD..FETCH_HEAD
to only see the remote commits since the local StGIT patches are
always seen as commits on top of the FETCH_HEAD. It's also useful for
people using 'git rebase'.
--
Catalin
next prev parent reply other threads:[~2005-08-08 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 19:44 use of temporary refs in resolve Junio C Hamano
2005-08-07 20:02 ` Linus Torvalds
2005-08-07 20:12 ` Junio C Hamano
2005-08-07 20:18 ` Linus Torvalds
2005-08-08 8:50 ` Catalin Marinas [this message]
2005-08-08 9:06 ` Junio C Hamano
2005-08-08 10:26 ` Catalin Marinas
2005-08-09 2:48 ` Junio C Hamano
2005-08-09 9:07 ` Catalin Marinas
2005-08-09 12:51 ` Junio C Hamano
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=tnxk6iwx161.fsf@arm.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).