From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/7] Clean up interpret_nth_last_branch feature
Date: Sat, 21 Mar 2009 15:13:32 -0700 [thread overview]
Message-ID: <1237673619-12608-1-git-send-email-gitster@pobox.com> (raw)
Dscho and Pasky seem to want to introduce %name and there were a few
discussions around this area, mostly on the syntax.
I am not personally interested in the implementation of this new feature
itself, but I would want to solidify the codepath that they will be
building on before accepting any patch for it, because I have a stake at
the overall health of the resulting code we need to maintain.
The first one is what I already sent. The last one is a bit iffy.
Junio C Hamano (7):
check_ref_format(): tighten refname rules
Rename interpret/substitute nth_last_branch functions
check-ref-format --branch: give Porcelain a way to grok branch
shorthand
strbuf_branchname(): a wrapper for branch name shorthands
Fix branch -m @{-1} newname
strbuf_check_branch_ref(): a helper to check a refname for a branch
checkout -: make "-" to mean "previous branch" everywhere
branch.c | 10 +---------
builtin-branch.c | 20 ++++++--------------
builtin-check-ref-format.c | 9 +++++++++
builtin-checkout.c | 26 +++++++++++---------------
builtin-merge.c | 5 ++---
cache.h | 2 +-
refs.c | 12 ++++++++----
sha1_name.c | 33 +++++++++++++++++++--------------
strbuf.c | 17 +++++++++++++++++
strbuf.h | 3 +++
10 files changed, 77 insertions(+), 60 deletions(-)
next reply other threads:[~2009-03-21 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 22:13 Junio C Hamano [this message]
2009-03-21 22:13 ` [PATCH 1/7] check_ref_format(): tighten refname rules Junio C Hamano
2009-03-21 22:13 ` [PATCH 2/7] Rename interpret/substitute nth_last_branch functions Junio C Hamano
2009-03-21 22:13 ` [PATCH 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand Junio C Hamano
2009-03-21 22:13 ` [PATCH 4/7] strbuf_branchname(): a wrapper for branch name shorthands Junio C Hamano
2009-03-21 22:13 ` [PATCH 5/7] Fix "branch -m @{-1} newname" Junio C Hamano
2009-03-21 22:13 ` [PATCH 6/7] strbuf_check_branch_ref(): a helper to check a refname for a branch Junio C Hamano
2009-03-21 22:13 ` [PATCH 7/7] checkout -: make "-" to mean "previous branch" everywhere Junio C Hamano
2009-03-22 0:58 ` [PATCH 7/7 (v2)] " Junio C Hamano
2009-03-22 10:18 ` [PATCH 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand Bert Wesarg
2009-03-22 21:58 ` Junio C Hamano
2009-03-21 23:15 ` [PATCH 1/7] check_ref_format(): tighten refname rules Junio C Hamano
2009-03-22 14:41 ` Johannes Schindelin
2009-03-22 23:19 ` 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=1237673619-12608-1-git-send-email-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.