git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Stefano Lattarini <stefano.lattarini@gmail.com>
Subject: Re: [PATCH v5 2/2] Add new @ shortcut for HEAD
Date: Tue, 03 Sep 2013 11:50:49 -0700	[thread overview]
Message-ID: <xmqqd2opsprq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1378103670-3394-3-git-send-email-felipe.contreras@gmail.com> (Felipe Contreras's message of "Mon, 2 Sep 2013 01:34:30 -0500")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> diff --git a/sha1_name.c b/sha1_name.c
> index 93197b9..b8ece6e 100644
> --- a/sha1_name.c
> +++ b/sha1_name.c
> @@ -1004,6 +1004,26 @@ int get_sha1_mb(const char *name, unsigned char *sha1)
>  	return st;
>  }
>  
> +/* parse @something syntax, when 'something' is not {.*} */
> +static int interpret_empty_at(const char *name, int namelen, int len, struct strbuf *buf)
> +{
> +	const char *next;
> +
> +	if (len || name[1] == '{')
> +		return -1;
> +
> +	/* make sure it's a single @, or @@{.*}, not @foo */
> +	next = strchr(name + len + 1, '@');
> +	if (!next)
> +		next = name + namelen;
> +	if (next != name + 1)
> +		return -1;
> +
> +	strbuf_reset(buf);
> +	strbuf_add(buf, "HEAD", 4);
> +	return 1;
> +}

Hmph, is the above sufficient?  I added a case that mimics Stefano's
original regression report (which is handled) and another that uses
doubled "@" for the same purpose of introducing a "funny" hierarchy,
and it appears that "checkout -b" chokes on it.

 t/t1508-at-combinations.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/t/t1508-at-combinations.sh b/t/t1508-at-combinations.sh
index 3a52375..ceb8449 100755
--- a/t/t1508-at-combinations.sh
+++ b/t/t1508-at-combinations.sh
@@ -32,6 +32,8 @@ test_expect_success 'setup' '
 	git checkout -b upstream-branch &&
 	test_commit upstream-one &&
 	test_commit upstream-two &&
+	git checkout -b @/at-test &&
+	git checkout -b @@/at-test &&
 	git checkout -b @at-test &&
 	git checkout -b old-branch &&
 	test_commit old-one &&
@@ -58,6 +60,8 @@ check "@{-1}@{u}" ref refs/heads/master
 check "@{-1}@{u}@{1}" commit master-one
 check "@" commit new-two
 check "@@{u}" ref refs/heads/upstream-branch
+check "@@/at-test" ref refs/heads/@@/at-test
+check "@/at-test" ref refs/heads/@/at-test
 check "@at-test" ref refs/heads/@at-test
 nonsense "@{u}@{-1}"
 nonsense "@{0}@{0}"

  reply	other threads:[~2013-09-03 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02  6:34 [PATCH v5 0/2] Add @ shortcut, again Felipe Contreras
2013-09-02  6:34 ` [PATCH v5 1/2] sha1-name: pass len argument to interpret_branch_name() Felipe Contreras
2013-09-03 18:40   ` Junio C Hamano
2013-09-02  6:34 ` [PATCH v5 2/2] Add new @ shortcut for HEAD Felipe Contreras
2013-09-03 18:50   ` Junio C Hamano [this message]
2013-09-09  2:09     ` Felipe Contreras
2013-09-09 22:54       ` Junio C Hamano
2013-09-10 22:08         ` 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=xmqqd2opsprq.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=stefano.lattarini@gmail.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).