From: Steffen Prohaska <prohaska@zib.de>
To: git@vger.kernel.org
Subject: [REPLACEMENT PATCH 0/6] improve refspec handling in push, refactor matching in fetch
Date: Sun, 11 Nov 2007 15:01:42 +0100 [thread overview]
Message-ID: <1194789708646-git-send-email-prohaska@zib.de> (raw)
This is a replacement for sp/push-refspec. It is rebased to the current master.
Documentation/git-push.txt | 4 ++--
Documentation/git-send-pack.txt | 4 +++-
builtin-push.c | 11 +++++++++++
cache.h | 4 ++++
refs.c | 31 +++++++++++++++++++++++++++++++
remote.c | 28 +++-------------------------
sha1_name.c | 14 ++------------
t/t5510-fetch.sh | 25 +++++++++++++++++++++++++
t/t5516-fetch-push.sh | 29 ++++++++++++++++++++++++++++-
transport.c | 8 ++++++--
transport.h | 1 +
11 files changed, 116 insertions(+), 43 deletions(-)
[PATCH 1/6] push: mention --verbose option in documentation
Push uses parseopts, which supports '--verbose'.
[PATCH 2/6] push: teach push to pass --verbose option to transport layer
Adapted to paresopts changes.
[PATCH 3/6] push: support pushing HEAD to real branch name
Same as before.
[PATCH 4/6] add ref_abbrev_matches_full_with_rules()
[PATCH 5/6] push: use same rules as git-rev-parse to resolve refspecs
[PATCH 6/6] refactor fetch's ref matching to use ref_abbrev_matches_full_with_rules()
Start unification of refspec matching rules.
next reply other threads:[~2007-11-11 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 14:01 Steffen Prohaska [this message]
2007-11-11 14:01 ` [PATCH 1/6] push: mention --verbose option in documentation Steffen Prohaska
2007-11-11 14:01 ` [PATCH 2/6] push: teach push to pass --verbose option to transport layer Steffen Prohaska
2007-11-11 14:01 ` [PATCH 3/6] push: support pushing HEAD to real branch name Steffen Prohaska
2007-11-11 14:01 ` [PATCH 4/6] add ref_abbrev_matches_full_with_rules() Steffen Prohaska
2007-11-11 14:01 ` [PATCH 5/6] push: use same rules as git-rev-parse to resolve refspecs Steffen Prohaska
2007-11-11 14:01 ` [PATCH 6/6] refactor fetch's ref matching to use ref_abbrev_matches_full_with_rules() Steffen Prohaska
2007-11-11 14:55 ` Jakub Narebski
2007-11-11 17:31 ` Steffen Prohaska
2007-11-12 19:51 ` [PATCH 5/6] push: use same rules as git-rev-parse to resolve refspecs Junio C Hamano
2007-11-12 20:48 ` Steffen Prohaska
2007-11-12 19:51 ` [PATCH 4/6] add ref_abbrev_matches_full_with_rules() Junio C Hamano
2007-11-12 20:51 ` Steffen Prohaska
2007-11-11 14:17 ` [PATCH 3/6] push: support pushing HEAD to real branch name Andreas Ericsson
2007-11-11 14:35 ` [REPLACEMENT PATCH " Steffen Prohaska
2007-11-11 14:10 ` [PATCH 1/6] push: mention --verbose option in documentation Steffen Prohaska
2007-11-11 14:14 ` Steffen Prohaska
2007-11-11 19:39 ` 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=1194789708646-git-send-email-prohaska@zib.de \
--to=prohaska@zib.de \
--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).