Hi, On Sat, 29 Sep 2007, Tom Prince wrote: > > > You could stash untracked files that are not ignored (I personally > > > ignore *.o, *.a and the like). > > > > And what if you happen to forget to ignore that? Or if you happen to > > have an strace log in some file (which you did not ignore either)? > > > > Thanks, but I think the semantics of git stash is pretty well defined. > > And it means that you stash away _tracked_ content that was not yet > > committed. > > > > I mean, you can have your desired behaviour with > > > > $ git add . > > $ git stash > > > > but if we were to fulfil your wish and change the default behaviour, > > there is no way back to the current behaviour (which I happen to find > > pretty sane). > > But > > git add . > git stash > git stash apply > > will not be a no-op any more. It never was. (Or did you mean "git stash apply --index"?) > It doesn't need to be a default, but there are certainly times when I > would find the option to stash untracked files convenient. But then I'll have to ask you why the untracked files, which are not touched by git, have to be stashed anyway? I'm seriously thinking that we are in deep "XY problem" land here. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
