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

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

From: Karl Hasselström <hidden>
Date: 2016-06-15 22:42:19

Possibly related (same subject, not in this thread)

On 2006-02-15 17:25:30 +0000, Catalin Marinas wrote:
On 14/02/06, Petr Baudis [off-list ref] wrote:
quoted
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.
This is a sensible way of using an uncommit command but I initially
thought it would be better to make things harder for people wanting
to re-write the history. Anyway, I'll keep this command on my todo
list.
stgit rewrites history all the time anyway. And as far as I recall,
there's nothing in the documentation that warns the user not to
publish stgit-managed branches. :-)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help