From: Junio C Hamano <gitster@pobox.com>
To: "Jan Krüger" <jk@jk.gs>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: [PATCH RFC] builtin-push: add --delete as syntactic sugar for :foo
Date: Mon, 09 Nov 2009 08:59:53 -0800 [thread overview]
Message-ID: <7v8wefy6pi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20091109130935.2bea7771@perceptron> ("Jan Krüger"'s message of "Mon\, 9 Nov 2009 13\:09\:35 +0100")
Jan Krüger <jk@jk.gs> writes:
> Refspecs without a source side have been reported as confusing by many.
> As an alternative, this adds support for commands like:
>
> git push origin --delete somebranch
>
> Specifically, --delete will prepend a colon to all colon-less refspecs
> given on the command line.
Will it barf and error out if there is any colon-ful one? I think it
should. I was about to write "I guess it could be argued both ways", but
after thinking about it for 5 seconds I do not see a sane way to explain a
command line "push origin --delete one two:three".
I agree with you that it wouldn't make sense to mix this with --all and
friends.
next prev parent reply other threads:[~2009-11-09 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 12:09 [PATCH RFC] builtin-push: add --delete as syntactic sugar for :foo Jan Krüger
2009-11-09 16:59 ` Junio C Hamano [this message]
2009-11-09 17:08 ` Junio C Hamano
2009-11-09 17:20 ` Sverre Rabbelier
2009-11-09 18:20 ` [PATCH RFC v2] " Jan Krüger
2009-12-29 11:05 ` Nanako Shiraishi
2009-12-29 16:58 ` Junio C Hamano
2009-12-30 9:52 ` [PATCH v3] " Jan Krüger
2009-12-30 12:14 ` Sverre Rabbelier
2009-12-30 19:49 ` Junio C Hamano
2009-12-30 19:57 ` [PATCH v4] " Jan Krüger
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=7v8wefy6pi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
/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).