From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 6/7] check_ref_format(): tighten refname rules
Date: Mon, 23 Mar 2009 09:03:42 -0700 [thread overview]
Message-ID: <7vd4c86xb5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090323135901.GB9732@spearce.org> (Shawn O. Pearce's message of "Mon, 23 Mar 2009 06:59:01 -0700")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Junio C Hamano <gitster@pobox.com> wrote:
>> This changes the rules for refnames to forbid:
>>
>> (1) a refname that contains "@{" in it.
>> (2) a refname that ends with a dot.
>
> How about also "that end in .lock" ?
Yeah, people can add more as follow-up patches. The primary purpose of
this series is to clean-up places that the new %name notation (or ~name or
whatever) needs to hook into.
next prev parent reply other threads:[~2009-03-23 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 7:58 [PATCH v2 0/7] Clean up interpret_nth_last_branch feature Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 1/7] Rename interpret/substitute nth_last_branch functions Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 2/7] strbuf_branchname(): a wrapper for branch name shorthands Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 4/7] Fix branch -m @{-1} newname Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 5/7] strbuf_check_branch_ref(): a helper to check a refname for a branch Junio C Hamano
2009-03-23 7:58 ` [PATCH v2 6/7] check_ref_format(): tighten refname rules Junio C Hamano
2009-03-23 13:59 ` Shawn O. Pearce
2009-03-23 16:03 ` Junio C Hamano [this message]
2009-03-23 7:58 ` [PATCH v2 7/7] checkout -: make "-" to mean "previous branch" everywhere Junio C Hamano
2009-03-23 8:10 ` [PATCH v2 0/7] Clean up interpret_nth_last_branch feature 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=7vd4c86xb5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.