From: Jay Soffian <jaysoffian@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: FETCH_HEAD question
Date: Tue, 17 Feb 2009 12:34:18 -0500 [thread overview]
Message-ID: <76718490902170934u5e2c17ffl7599ddeb5ee59812@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902171821190.6185@intel-tinevez-2-302>
On Tue, Feb 17, 2009 at 12:22 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>> Unless dwim_ref() is updated to handle FETCH_HEAD specially, and
>> return not the first SHA1, but the one not marked "not-for-merge".
>> Then the UI would at least be consistent, but this would not be
>> backward compatible.
>
> You cannot fix parsing FETCH_HEAD as a ref (and neither will you be able
> to do with PUSH_HEAD), as it can contain _more_ than one SHA-1s. This
> still holds true when ignoring the not-for-merge lines, as an octopus is
> a quite real possibility.
An even better argument against than it not being backward compatible. :-)
And there is no PUSH_HEAD.
j.
next prev parent reply other threads:[~2009-02-17 17:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 4:43 FETCH_HEAD question Jay Soffian
2009-02-17 5:11 ` Jay Soffian
2009-02-17 5:36 ` Junio C Hamano
2009-02-17 6:21 ` Jay Soffian
2009-02-17 7:18 ` Junio C Hamano
2009-02-17 7:41 ` Jay Soffian
2009-02-17 8:35 ` Junio C Hamano
2009-02-17 17:14 ` Jay Soffian
2009-02-17 17:22 ` Johannes Schindelin
2009-02-17 17:34 ` Jay Soffian [this message]
2009-02-17 22:58 ` PUSH_HEAD, was " Johannes Schindelin
2009-02-17 23:43 ` Junio C Hamano
2009-02-18 0:29 ` Jay Soffian
2009-02-18 0:30 ` Johannes Schindelin
2009-02-17 8:25 ` Sitaram Chamarty
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=76718490902170934u5e2c17ffl7599ddeb5ee59812@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).