Re: git-kill: rewrite history removing a commit

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Michael S. Tsirkin <mst@...>
Cc: Junio C Hamano <junkio@...>, <git@...>
Date: Wednesday, January 31, 2007 - 4:22 pm

On Wed, Jan 31, 2007 at 09:55:33PM +0200, Michael S. Tsirkin wrote:

That may be well when no patch depends on the one you kill.  In that
case, it surely requires some work to handfix things.

I'd suggest to use stgit to prepare commits before publication.  Even
if you don't feel the need for it in everyday life, you can have a
one-shot use for this particular problem, by turning your latest
commits into an stgit stack, use stgit facilities to handle posible
conflicts, and turn them into commits again:

The nominal case goes:

  stg init
  stg uncommit -n <ncommits>
  stg float <patch-to-kill>
  stg delete <patch-to-kill>

And if there is any conflict, you can still solve them, decide to
change your plans, get diffs from gitk, etc.

Best regards,
-- 
Yann.
-
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.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git-kill: rewrite history removing a commit, Michael S. Tsirkin, (Wed Jan 31, 3:55 pm)
Re: git-kill: rewrite history removing a commit, Junio C Hamano, (Wed Jan 31, 4:26 pm)
Re: git-kill: rewrite history removing a commit, Michael S. Tsirkin, (Wed Jan 31, 4:54 pm)
Re: git-kill: rewrite history removing a commit, Yann Dirson, (Wed Jan 31, 4:22 pm)
Re: git-kill: rewrite history removing a commit, Catalin Marinas, (Thu Feb 1, 8:41 am)