>
> So you would naturally be tempted to do this:
>
> ... Re-edit, compile, and test. This time it is perfect.
> $ git commit -a -C ORIG_HEAD
>
> Well, not really. You can lose any file newly created in
> ORIG_HEAD this way. Instead, you need to do this:
>
> ... Re-edit, compile, and test. This time it is perfect.
> $ git add <whatever file you have changed>
> $ git commit -a -C ORIG_HEAD
>
> Do people find this a big problem?
I often do some maybe not that brilliant changes in my tree,
and when I then ask git to reset these I expect git to reset
everything.
After a git-reset HEAD^ I really expect git to have rewinded back till
where I started with no files added whatsoever.
>From the matter of least suprise git should not remember files added,
one have to do that by themself again if needed.
Sam
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
