From: Boris Faure <billiob@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH/RFC] branch: add optional parameter to -r to specify remote
Date: Sun, 19 Jun 2011 21:19:08 +0200 [thread overview]
Message-ID: <1308511149-10933-1-git-send-email-billiob@gmail.com> (raw)
The following patch adds an optional parameter to branch -r to use as
-r=<remote> in order to list branches on a particular remote.
'git branch -d -r one/another' can also be done with
'git branch -d -r=one another'.
I haven't found tests specially crafted for 'git branch -r -d <branch>'. I
hope the tests I have added are in the correct places.
next reply other threads:[~2011-06-19 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 19:19 Boris Faure [this message]
2011-06-19 19:19 ` [PATCH/RFC] branch: add optional parameter to -r to specify remote Boris Faure
2011-06-19 22:32 ` Junio C Hamano
2011-06-20 6:40 ` Johannes Sixt
2011-06-20 7:03 ` Jeff King
2011-06-20 11:08 ` Michael J Gruber
2011-06-20 13:09 ` Jeff King
2011-06-20 15:42 ` Junio C Hamano
2011-06-20 16:59 ` [PATCH] tag: accept multiple patterns for --list Jeff King
2011-06-20 15:49 ` [PATCH/RFC] branch: add optional parameter to -r to specify remote Junio C Hamano
2011-06-20 15:39 ` Junio C Hamano
2011-06-20 19:12 ` Boris Faure
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=1308511149-10933-1-git-send-email-billiob@gmail.com \
--to=billiob@gmail.com \
--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).