Re: [RFC/WIP PATCH 05/11] transport: add infrastructure to support a protocol version number
- From
Jeff King <peff@peff.net>
- Date
- May 27, 2015, 06:39 UTC
- Message-ID
- <20150527063925.GC885@peff.net>
- In-Reply-To
- <1432677675-5118-6-git-send-email-sbeller@google.com>
On Tue, May 26, 2015 at 03:01:09PM -0700, Stefan Beller wrote:
> + OPT_STRING('y', "transport-version", &transport_version,
> + N_("transport-version"),
> + N_("specify transport version to be used")),Interesting choice for the short option ("-v" would be nice, but obviously it is taken). Do we want to delay on claiming the short-and-sweet 'y' until we are sure this is something people will use a lot? In an ideal world, it is not (i.e., auto-upgrade and other tricks become good enough that nobody bothers to specify it manually).
-Peff