On Mon, Mar 25, 2013 at 1:17 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: >> +--sparse:: >> + In sparse checkout mode, `git checkout -- <paths>` would >> + update all entries matched by <paths> regardless sparse >> + patterns. This option only updates entries matched by <paths> >> + and sparse patterns. > > Hm, should this be the default? > > In principle, I would expect > > git checkout -- . > > to make the worktree match the index, respecting the sparse checkout. > And something like > > git checkout --widen -- . > > to change the sparse checkout pattern. But of course it is easily > possible that I am missing some details of how sparse checkout is > used in practice. > > What do you think?
Changing the default may involve a painful transition phase (e.g. "add -u"). I think making it the default via alias should be good enough in most cases. We also need to think how it impacts checkout usage in scripts. I think it might be ok, but I haven't finished my morning coffee yet, so.. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
