From: Junio C Hamano <gitster@pobox.com>
To: Joey Hess <joey@kitenet.net>
Cc: git@vger.kernel.org
Subject: Re: FETCH_HEAD documentation vs reality
Date: Mon, 26 Dec 2011 00:16:04 -0800 [thread overview]
Message-ID: <7vd3bb929n.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20111225173901.GA668@gnu.kitenet.net> (Joey Hess's message of "Sun, 25 Dec 2011 13:39:01 -0400")
Joey Hess <joey@kitenet.net> writes:
> Or yet another way to fix it would be to make git fetch always write the
> intended FETCH_HEAD first into .git/FETCH_HEAD. (When not in --append mode.)
> This seems like perhaps the best fix,...
Sounds good, if you mean "the first one that is marked as for-merge" by
"intended FETCH_HEAD".
Thanks. Please make it so.
next prev parent reply other threads:[~2011-12-26 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 17:39 FETCH_HEAD documentation vs reality Joey Hess
2011-12-26 8:16 ` Junio C Hamano [this message]
2011-12-26 16:16 ` [PATCH] write first for-merge ref to FETCH_HEAD first Joey Hess
2011-12-27 18:44 ` Junio C Hamano
2012-01-03 23:57 ` Junio C Hamano
2012-01-04 0:03 ` Joey Hess
2012-01-04 0:12 ` 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=7vd3bb929n.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
/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).