From: Jakub Narebski <jnareb@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] add a --delete option to git push
Date: Fri, 14 Aug 2009 22:25:38 +0200 [thread overview]
Message-ID: <200908142225.38610.jnareb@gmail.com> (raw)
In-Reply-To: <fabb9a1e0908140953w2d3f571cv3e7415817c2758a7@mail.gmail.com>
Dnia piątek 14. sierpnia 2009 18:53, Sverre Rabbelier napisał:
> 2009/8/14 Jakub Narebski <jnareb@gmail.com>:
>> On Fri, 14 August 2009, Sverre Rabbelier wrote:
>>>
>>> This is in reply to a brief conversation I had with jnareb on #git
>>> about the blogpost "5 things git could learn from hg", or something
>>> like that (can't find it right now).
>>
>> Thanks.
>
> What do you think would be the best solution? There seem to be a lot
> of opinions on how to proceed.
I think we can begin with simple and strict: "--delete=<branch>"
is long version of equivalent ":<branch>" (like long option equivalent
to short one).
--
Jakub Narebski
Poland
prev parent reply other threads:[~2009-08-14 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 5:05 [RFC PATCH 0/2] add a --delete option to git push Sverre Rabbelier
2009-08-14 5:05 ` [RFC PATCH 1/2] " Sverre Rabbelier
2009-08-14 5:05 ` [RFC PATCH 2/2] test that git push --delete deletes the remote ref Sverre Rabbelier
2009-08-14 5:21 ` [RFC PATCH 1/2] add a --delete option to git push Jeff King
2009-08-14 6:24 ` Sverre Rabbelier
2009-08-14 6:33 ` Jeff King
2009-08-14 6:40 ` Sverre Rabbelier
2009-08-14 6:55 ` Jeff King
2009-08-14 6:53 ` Junio C Hamano
2009-08-14 7:00 ` Jeff King
2009-08-14 7:01 ` Jeff King
2009-08-14 7:05 ` Sverre Rabbelier
2009-08-14 7:51 ` Junio C Hamano
2009-08-15 2:01 ` Junio C Hamano
2009-08-16 2:30 ` Sverre Rabbelier
2009-08-16 9:19 ` Jakub Narebski
2009-08-14 8:50 ` [RFC PATCH 0/2] " Jakub Narebski
[not found] ` <fabb9a1e0908140953w2d3f571cv3e7415817c2758a7@mail.gmail.com>
2009-08-14 20:25 ` Jakub Narebski [this message]
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=200908142225.38610.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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