From: Michael Schubert <mschub@elegosoft.com>
To: git@vger.kernel.org
Subject: [PATCH] refname format cleanup
Date: Mon, 16 Jul 2012 14:12:59 +0200 [thread overview]
Message-ID: <1342440781-18816-1-git-send-email-mschub@elegosoft.com> (raw)
Previous discussion:
http://thread.gmane.org/gmane.comp.version-control.git/200129/focus=200146
I'm not sure if I've drawn the right conclusions from the previous
thread, so please let me know in case that's the wrong way to go..
* refs: disallow ref components starting with hyphen
* symbolic-ref: check format of given refname
builtin/symbolic-ref.c | 4 +++-
builtin/tag.c | 3 ---
refs.c | 2 ++
sha1_name.c | 2 --
t/t1401-symbolic-ref.sh | 10 ++++++++++
5 files changed, 15 insertions(+), 6 deletions(-)
next reply other threads:[~2012-07-16 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 12:12 Michael Schubert [this message]
2012-07-16 12:13 ` [PATCH 1/2] refs: disallow ref components starting with hyphen Michael Schubert
2012-07-16 13:18 ` Michael Haggerty
2012-07-16 17:06 ` Junio C Hamano
2012-07-16 17:49 ` Junio C Hamano
2012-07-16 12:13 ` [PATCH 2/2] symbolic-ref: check format of given refname Michael Schubert
2012-07-16 13:24 ` Michael Haggerty
2012-07-16 17:12 ` 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=1342440781-18816-1-git-send-email-mschub@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).