git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Steffen Prohaska <prohaska@zib.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/8] push: change push to fail if short ref name does not exist
Date: Sat, 27 Oct 2007 17:42:24 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710271716120.7345@iabervon.org> (raw)
In-Reply-To: <11935038081211-git-send-email-prohaska@zib.de>

On Sat, 27 Oct 2007, Steffen Prohaska wrote:

> You can use a branch's shortname to push it. Push used to create
> the branch on the remote side if it did not yet exist. If you
> specified the wrong branch accidentally it was created. A safety
> valve that pushes only existing branches may help to avoid
> errors.
> 
> This commit changes push to fail if the remote ref does not yet
> exist and the refspec does not start with refs/. Remote refs must
> explicitly be created with their full name.

I agree with the change (and I think it's appropriate for master or next), 
but your implementation is a bit too clever for my tastes.

> Signed-off-by: Steffen Prohaska <prohaska@zib.de>
> ---
>  remote.c              |    5 +++--
>  t/t5516-fetch-push.sh |   34 ++++++++++++++++++++++++++++++++--
>  2 files changed, 35 insertions(+), 4 deletions(-)
> 
> diff --git a/remote.c b/remote.c
> index 170015a..ec992c9 100644
> --- a/remote.c
> +++ b/remote.c
> @@ -611,6 +611,7 @@ static int match_explicit(struct ref *src, struct ref *dst,
>  	struct ref *matched_src, *matched_dst;
>  
>  	const char *dst_value = rs->dst;
> +	const char * const orig_dst_value = rs->dst ? rs->dst : rs->src;

"lit_dst_value" would probably be a better description, and it might be 
worth handling the rs->dst == NULL case where it's handled for dst_value. 
Technically, this variable, when it doesn't match the final value of 
dst_value, has a value that dst_value never had.

>  
>  	if (rs->pattern)
>  		return errs;
> @@ -647,12 +648,12 @@ static int match_explicit(struct ref *src, struct ref *dst,
>  	case 1:
>  		break;
>  	case 0:
> -		if (!memcmp(dst_value, "refs/", 5))
> +		if (!memcmp(orig_dst_value , "refs/", 5))
>  			matched_dst = make_linked_ref(dst_value, dst_tail);

This should also be orig_dst_value, too. I know that dst_value and 
orig_dst_value must be the same in this case, but it takes a bunch of 
analysis to demonstrate that, and it's more intuitive to use the value 
you've just checked anyway, and also to have all of case 0 use the 
differently-computed destination.

>  		else
>  			error("dst refspec %s does not match any "
>  			      "existing ref on the remote and does "
> -			      "not start with refs/.", dst_value);
> +			      "not start with refs/.", orig_dst_value);

Maybe the error should provide a hint if dst_value is not the same as 
orig_dst_value? (if (!rs->dst) error("Did you mean %s?\n", dst_value);)

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2007-10-27 21:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27 16:49 [PATCH 0/8 v2] improve push's refspec handling Steffen Prohaska
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   ` Daniel Barkalow [this message]
2007-10-28  7:28   ` [PATCH 1/8] push: change push to fail if short ref name does not exist 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=Pine.LNX.4.64.0710271716120.7345@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=prohaska@zib.de \
    /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).