From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/7] Clean up interpret_nth_last_branch feature
Date: Mon, 23 Mar 2009 00:58:33 -0700 [thread overview]
Message-ID: <cover.1237791716.git.gitster@pobox.com> (raw)
The changes since the previous round are:
- Tightening of the refname rule comes very late in the series, so that
we can optionally drop it;
- In addition to allowing "git branch -d bad@{name}ref.", we also allow
"git branch -d bad@{name}ref. good-one" as another escape hatch;
- Update documentation to git-check-ref-format to describe the tightened
rules.
Junio C Hamano (7):
Rename interpret/substitute nth_last_branch functions
strbuf_branchname(): a wrapper for branch name shorthands
check-ref-format --branch: give Porcelain a way to grok branch
shorthand
Fix branch -m @{-1} newname
strbuf_check_branch_ref(): a helper to check a refname for a branch
check_ref_format(): tighten refname rules
checkout -: make "-" to mean "previous branch" everywhere
Documentation/git-check-ref-format.txt | 18 ++++++++++++++++-
branch.c | 10 +--------
builtin-branch.c | 32 +++++++++++++++++-------------
builtin-check-ref-format.c | 9 ++++++++
builtin-checkout.c | 26 ++++++++++--------------
builtin-merge.c | 5 +--
cache.h | 2 +-
refs.c | 16 +++++++++++---
sha1_name.c | 33 ++++++++++++++++++-------------
strbuf.c | 17 ++++++++++++++++
strbuf.h | 3 ++
11 files changed, 110 insertions(+), 61 deletions(-)
next reply other threads:[~2009-03-23 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 7:58 Junio C Hamano [this message]
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
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=cover.1237791716.git.gitster@pobox.com \
--to=gitster@pobox.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 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.