mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <>
To: Junio C Hamano <>, Philip Oakley <>
Cc: GitList <>, "Duy Nguyen" <>,
	"Ævar Arnfjörð Bjarmason" <>
Subject: Re: [RFC/PATCH v2] doc branch: provide examples for listing remote tracking branches
Date: Fri, 14 Jun 2019 22:00:52 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Junio,

On 10/06/2019 18:57, Junio C Hamano wrote:
> Philip Oakley <> writes:
>> The availability of these pattern selections is not obvious from
>> the man pages, as per mail thread <>.
>> Provide examples.
>> Re-order the `git branch` synopsis to emphasise the `--list <pattern>`
>> pairing. Also expand and reposition the `all/remotes` options.
>> Split the over-long description into three parts so that the <pattern>
>> description can be seen.
>> Clarify that the `all/remotes` options require the --list if patterns
>> are to be used.
>> Add examples of listing remote tracking branches that match a pattern,
>> including `git for-each-ref` which has more options.
>> Improve the -a/-r warning message. The message confused this author
>> as the combined -a and -r options had not been given, though a pattern
>> had. Specifically guide the user that maybe they needed the --list
>> option to enable a remote branch pattern selection.
>> Signed-off-by: Philip Oakley <>
>> ---
>> in response to
>> <>
>> thread:
>> to: Git Mailing List <>
>> cc: Duy Nguyen <>
>> cc: Ævar Arnfjörð Bjarmason <>
>> cc: Junio C Hamano <>
> This looks reasonable to me---is it ready to go even with its RFC prefix?

Yes; the RFC was only in regard of the die() message change as it 
touches real code;-)

Following the post, Stolee's coverage report, it was noted that the 
die() wasn't actually tested, so I sent a quick follow-up of a potential 
which is a proper RFC...

I did not attempt to see if any other dies()'s were untested, just 
copied one that was..


(currently travelling)

  reply	other threads:[~2019-06-14 21:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 15:16 Command to list <pattern> Branches on a specific Remote (i.e. select from rtb's) Philip Oakley
2019-05-18 18:37 ` Ævar Arnfjörð Bjarmason
2019-05-18 19:44   ` Philip Oakley
2019-05-19  3:07     ` Duy Nguyen
2019-05-19  9:49       ` Philip Oakley
2019-05-28 12:13       ` [PATCH] doc branch: provide examples for listing remote tracking branches Philip Oakley
2019-05-28 13:58         ` Junio C Hamano
2019-05-28 14:17           ` Philip Oakley
2019-05-28 14:51             ` Philip Oakley
2019-05-28 15:51               ` Junio C Hamano
2019-05-28 16:17                 ` Philip Oakley
2019-05-28 23:16                   ` [RFC/PATCH v2] " Philip Oakley
2019-06-10 17:57                     ` Junio C Hamano
2019-06-14 21:00                       ` Philip Oakley [this message]
2019-05-19  3:05   ` Command to list <pattern> Branches on a specific Remote (i.e. select from rtb's) Duy Nguyen
2019-05-28 13:57   ` Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).