Re: [1.8.0] make two-argument fetch update remote branches
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Feb 1, 2011, 15:58 UTC
- Message-ID
- <AANLkTinns+M1=50jj7RAFnnp6-WPv+CpuWkO0xq_qko9@mail.gmail.com>
- In-Reply-To
- <AANLkTi=Y9PBs_jXyCiAL9YLA8Y_jzWwqxw63hKm7fVBO@mail.gmail.com>
On Tue, Feb 1, 2011 at 2:04 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
Show 11 quoted lines
> On Mon, Jan 31, 2011 at 4:44 PM, Thomas Rast <trast@student.ethz.ch> wrote: >> Add a fetch.updateRemoteNamespace (or so) configuration variable that >> defaults to false. When enabled, it turns on the auto-updating >> behaviour. > > Would it make sense to group the pre-1.8 compatibility switches > together in some way, if there will be several of them? Maybe > > [compat] > fetchUpdateRemoteNamespace = false > ...
It is. I was thinking of it as a group of "short"-lived configs to help maintain backward compatibility for some time (not for ever) until users are forced to migrate.
-- Duy