Dear diary, on Tue, Feb 14, 2006 at 09:58:02PM CET, I got a letter where Chuck Lever <cel@citi.umich.edu> said that... > my impression of git is that you don't change stuff that's already > committed. you revert changes by applying a new commit that backs out > the original changes. i'm speculating, but i suspect that's why there's > a "stg pick --reverse" and not a "stg uncommit." It is ok as long as you know what are you doing - if you don't push out the commits you've just "undid" (or work on a public accessible repository in the first place, but I think that's kind of rare these days; quick survey - does anyone reading these lines do that?), there's nothing wrong on it, and it gives you nice flexibility. For example, to import bunch of patches (I guess that's the original intention behind this) you just run git-am on them and then stg uncommit all of the newly added commits. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Of the 3 great composers Mozart tells us what it's like to be human, Beethoven tells us what it's like to be Beethoven and Bach tells us what it's like to be the universe. -- Douglas Adams - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Feb 15 09:29:02 2006
This archive was generated by hypermail 2.1.8 : 2006-02-15 09:29:13 EST