git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Prohaska <prohaska@zib.de>
To: git@vger.kernel.org
Subject: [PATCH 0/8 v2] improve push's refspec handling
Date: Sat, 27 Oct 2007 18:49:59 +0200	[thread overview]
Message-ID: <119350380778-git-send-email-prohaska@zib.de> (raw)

This patch series improves the refspec handling in push.

It is a replacement for the series in sp/push-refspec
(666df53d6868bf56ca6c9ed0a927d612c67fe68c).

The series addresses some issues that were recently discussed on the
mailing list.
- creating remote refs requires a more explicit command [1].
- the current branch can be pushed as "git push HEAD" [2].
- matching of refs use same rules as git rev-parse [3].
- annoying error messages when working with shared repos are supressed [4].

[1] http://marc.info/?l=git&m=119286893014690&w=2
[2] http://marc.info/?l=git&m=119089831513994&w=2
[3] http://marc.info/?l=git&m=119224567631084&w=2
[4] http://marc.info/?t=119305127000001&r=1&w=2


Note, existing setups may break. Therefore, we need to decide if this
series can be applied before git 1.6.

All tests pass.

    Steffen

 Documentation/git-http-push.txt |    6 ++
 Documentation/git-push.txt      |    8 ++-
 Documentation/git-send-pack.txt |   18 ++++-
 builtin-push.c                  |    6 ++-
 builtin-rev-parse.c             |   27 +++++---
 cache.h                         |    2 +
 http-push.c                     |    9 ++-
 remote.c                        |   41 ++++++++----
 remote.h                        |    2 +-
 send-pack.c                     |   70 ++++++++++++++++-----
 sha1_name.c                     |   52 +++++++++++++----
 t/t5516-fetch-push.sh           |  127 ++++++++++++++++++++++++++++++++++++++-
 transport.c                     |    8 ++-
 transport.h                     |    1 +
 14 files changed, 311 insertions(+), 66 deletions(-)

 [PATCH 1/8] push: change push to fail if short ref name does not exist
 [PATCH 2/8] push: teach push new flag --create
    these two should be kept together.

 [PATCH 3/8] add get_sha1_with_real_ref() returning full name of ref on demand

 [PATCH 4/8] rev-parse: teach "git rev-parse --symbolic" to print the full ref name
    This one is a bit off-topic and could be skipped.

 [PATCH 5/8] push, send-pack: support pushing HEAD to real ref name

 [PATCH 6/8] add ref_cmp_full_short() comparing full ref name with a short name
 [PATCH 7/8] push: use same rules as git-rev-parse to resolve refspecs

 [PATCH 8/8] push: teach push to be quiet if local ref is strict subset of remote ref

             reply	other threads:[~2007-10-27 16:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27 16:49 Steffen Prohaska [this message]
2007-10-27 16:50 ` [PATCH 1/8] push: change push to fail if short ref name does not exist Steffen Prohaska
2007-10-27 16:50   ` [PATCH 2/8] push: teach push new flag --create Steffen Prohaska
2007-10-27 16:50     ` [PATCH 3/8] add get_sha1_with_real_ref() returning full name of ref on demand Steffen Prohaska
2007-10-27 16:50       ` [PATCH 4/8] rev-parse: teach "git rev-parse --symbolic" to print the full ref name Steffen Prohaska
2007-10-27 16:50         ` [PATCH 5/8] push, send-pack: support pushing HEAD to real " Steffen Prohaska
2007-10-27 16:50           ` [PATCH 6/8] add ref_cmp_full_short() comparing full ref name with a short name Steffen Prohaska
2007-10-27 16:50             ` [PATCH 7/8] push: use same rules as git-rev-parse to resolve refspecs Steffen Prohaska
2007-10-27 16:50               ` [PATCH 8/8] push: teach push to be quiet if local ref is strict subset of remote ref Steffen Prohaska
2007-10-28  7:28                 ` Junio C Hamano
2007-10-28  8:20                   ` Steffen Prohaska
2007-10-28  7:28               ` [PATCH 7/8] push: use same rules as git-rev-parse to resolve refspecs Junio C Hamano
2007-10-27 22:16             ` [PATCH 6/8] add ref_cmp_full_short() comparing full ref name with a short name Daniel Barkalow
2007-10-28  7:28             ` Junio C Hamano
2007-10-27 22:03           ` [PATCH 5/8] push, send-pack: support pushing HEAD to real ref name Daniel Barkalow
2007-10-28  7:28           ` Junio C Hamano
2007-10-28  8:03             ` Steffen Prohaska
2007-10-28 15:10             ` Steffen Prohaska
2007-10-28 15:40               ` Junio C Hamano
2007-10-28 15:59                 ` Steffen Prohaska
2007-10-28 16:03                 ` Junio C Hamano
2007-10-28 16:30                   ` Steffen Prohaska
2007-10-28 20:58                     ` Junio C Hamano
2007-10-31 15:08                       ` Steffen Prohaska
2007-10-27 21:53         ` [PATCH 4/8] rev-parse: teach "git rev-parse --symbolic" to print the full " Daniel Barkalow
2007-10-28 13:49           ` Steffen Prohaska
2007-10-28  7:28         ` Junio C Hamano
2007-10-28  7:58           ` Steffen Prohaska
2007-10-28  8:06             ` Shawn O. Pearce
2007-10-28  8:56               ` Steffen Prohaska
2007-10-28 15:10                 ` Brian Gernhardt
2007-10-28  8:24             ` Junio C Hamano
2007-10-28  7:28       ` [PATCH 3/8] add get_sha1_with_real_ref() returning full name of ref on demand Junio C Hamano
2007-10-27 21:42   ` [PATCH 1/8] push: change push to fail if short ref name does not exist Daniel Barkalow
2007-10-28  7:28   ` Junio C Hamano
2007-10-28  8:43     ` Steffen Prohaska

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=119350380778-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).