Re: [1.8.0] make two-argument fetch update remote branches
From: Jay Soffian <hidden>
Date: 2016-06-15 22:50:29
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [1.8.0] make two-argument fetch update remote branches · Matthieu Moy <hidden>
- 2016-06-15 · Re: [1.8.0] make two-argument fetch update remote branches · Junio C Hamano <hidden>
- 2016-06-15 · Re: [1.8.0] make two-argument fetch update remote branches · Junio C Hamano <hidden>
- 2016-06-15 · Re: [1.8.0] make two-argument fetch update remote branches · Eugene Sajine <hidden>
- 2016-06-15 · Re: [1.8.0] make two-argument fetch update remote branches · Junio C Hamano <hidden>
On Mon, Jan 31, 2011 at 4:44 PM, Thomas Rast [off-list ref] 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 ... (Thinking out loud.) j.