Git development
 help / color / mirror / Atom feed
From: normalperson@hand.yhbt.net (Eric Wong)
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio Hamano <junkio@cox.net>,
	git@vger.kernel.org, Martin Langhoff <martin.langhoff@gmail.com>
Subject: Re: [PATCH] Make '@' not valid in a ref name.
Date: Sat, 20 May 2006 19:00:38 -0700	[thread overview]
Message-ID: <20060521020038.GA22926@hand.yhbt.net> (raw)
In-Reply-To: <20060521013751.GA7516@spearce.org>

Shawn Pearce <spearce@spearce.org> wrote:
> Now that the sha1 expression syntax supports looking up a ref's
> value at a prior point in time through the '@' operator the '@'
> operator should not be permitted in a ref name.

This would break git-archimport (where email addresses are the first
part of the branch/tag names).

-- 
Eric Wong

  parent reply	other threads:[~2006-05-21  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21  1:37 [PATCH] Make '@' not valid in a ref name Shawn Pearce
2006-05-21  1:42 ` Junio C Hamano
2006-05-21  1:58   ` Shawn Pearce
2006-05-21  2:00 ` Eric Wong [this message]
2006-05-21  2:19   ` Shawn Pearce

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=20060521020038.GA22926@hand.yhbt.net \
    --to=normalperson@hand.yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=martin.langhoff@gmail.com \
    --cc=spearce@spearce.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