Thread (29 messages) flat view 29 messages, 9 authors, 2016-06-15

Re: [ANNOUNCE] pg - A patch porcelain for GIT

From: Petr Baudis <hidden>
Date: 2016-06-15 22:42:19

Possibly related (same subject, not in this thread)

Dear diary, on Tue, Feb 14, 2006 at 09:58:02PM CET, I got a letter
where Chuck Lever [off-list ref] 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help