Michael Sperber writes:
> git reset leaves the working copy alone. No patches applied or
> reversed, just an in-memory operation on the index, and a change of
> HEAD.
What's a situation where you'd want that? (I'm not doubting it exists,
just wondering.)
Fixing a typo or something in the last (unpublished commit) commit (so
you don't care if the ID changes, there are no references to it.
Forgetting a series of commits and mashing the whole thing into one
commit (I do this *a lot* because I forget to commit the ChangeLog).
You'd think it would be a purely internal operation, a building block
for more complex to implement but intuitively atomic operations. But
I find myself using it a fair amount.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta