From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/2] t1506: more test for @{upstream} syntax
Date: Thu, 28 Jan 2010 04:44:46 -0500 [thread overview]
Message-ID: <20100128094446.GA14244@coredump.intra.peff.net> (raw)
In-Reply-To: <7veilbqs82.fsf@alter.siamese.dyndns.org>
On Wed, Jan 27, 2010 at 11:10:21AM -0800, Junio C Hamano wrote:
> I wanted to do something like what your patch does by iterating over the
> input inside get_sha1_basic() while we still see @{...}, parsing pieces
> from the beginning, not from the end like the original "do we have the
> reflog indicator at the end? If so strip it and deal with what we have at
> the front". Your patch to i-b-n does that by recursing inside, which is a
> nice solution.
Yeah, I wanted to do that too, but it just ended up very messy. I
suppose the i-b-n solution is reasonably elegant, and it should
correctly handle non-get-sha1 instances like:
git checkout @{-1}@{u}
> Care to roll a patch with additional tests, to build on top of 105e473
> (Fix log -g this@{upstream}, 2010-01-26)?
Yep, series to follow:
[1/3]: test combinations of @{} syntax
[2/3]: fix parsing of @{-1}@{u} combination
[3/3]: reject @{-1} not at beginning of object name
-Peff
next prev parent reply other threads:[~2010-01-28 9:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:49 default behaviour for `gitmerge` (no arguments) Gareth Adams
2010-01-11 19:43 ` Junio C Hamano
2010-01-12 16:23 ` Jeff King
2010-01-12 18:11 ` Junio C Hamano
2010-01-12 18:25 ` Jeff King
2010-01-13 6:57 ` Junio C Hamano
2010-01-13 9:26 ` Johannes Schindelin
2010-01-13 9:47 ` Junio C Hamano
2010-01-13 11:04 ` Johannes Schindelin
2010-01-13 19:48 ` Junio C Hamano
2010-01-13 22:49 ` Johannes Schindelin
2010-01-13 23:13 ` Junio C Hamano
2010-01-20 9:38 ` [PATCH 0/2] @{u} updates Junio C Hamano
2010-01-20 9:38 ` [PATCH 1/2] t1506: more test for @{upstream} syntax Junio C Hamano
2010-01-26 13:07 ` Jeff King
2010-01-26 19:58 ` Junio C Hamano
2010-01-27 10:24 ` Jeff King
2010-01-27 18:50 ` Junio C Hamano
2010-01-28 8:52 ` Jeff King
2010-01-26 21:32 ` Junio C Hamano
2010-01-27 11:40 ` Jeff King
2010-01-27 19:10 ` Junio C Hamano
2010-01-28 9:44 ` Jeff King [this message]
2010-01-28 9:50 ` [PATCH 1/3] test combinations of @{} syntax Jeff King
2010-01-28 9:52 ` [PATCH 2/3] fix parsing of @{-1}@{u} combination Jeff King
2010-01-28 9:56 ` [PATCH 3/3] reject @{-1} not at beginning of object name Jeff King
2010-01-28 20:02 ` Junio C Hamano
2010-01-29 11:22 ` Jeff King
2010-01-20 9:38 ` [PATCH 2/2] Teach @{upstream} syntax to strbuf_branchanme() Junio C Hamano
2010-01-20 13:08 ` [PATCH 0/2] @{u} updates Johannes Schindelin
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=20100128094446.GA14244@coredump.intra.peff.net \
--to=peff@peff.net \
--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).