Re: Dropping '+' from fetch = +refs/heads/*:refs/remotes/origin/*?
- From
Shawn Pearce <spearce@spearce.org>
- Date
- Sep 1, 2011, 19:50 UTC
- Message-ID
- <CAJo=hJv4CkmaJuVvCA2VdO68zn4Xb9EQsdP8p1W-7B9zbvXSaQ@mail.gmail.com>
- In-Reply-To
- <vpqippcm4x4.fsf@bauges.imag.fr>
On Thu, Sep 1, 2011 at 12:35, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 7 quoted lines
> By asking users to explicitely say "yes, I know, this branch can be > rewond", we also ask them to think about it before making a mistake. > > That said, enabling the check by default may also become painful. I'd > vote for a configuration option, defaulting to the current behavior for > now. Then we can try living with it for a while and see how painful it > is.
I suspect the vast majority of branches in the wild do not rewind under normal conditions. Users who work against branches that rewind (e.g. those of us basing on a topic in pu) are already sophisticated enough with Git to understand what the fetch error would mean and fix it.
IMHO, just change the default in clone, and better, add a warning to fetch if that default pattern is still in the configuration file. Let the user either remove the wildcarded force fetch spec, or add a new configuration variable to his remote block to silence the warning.
-- Shawn.