All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Editing patch sequences
Date: Sun, 16 Mar 2008 12:02:55 +0100	[thread overview]
Message-ID: <87r6eb0w4g.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <m3myp8fdae.fsf@localhost.localdomain> (Jakub Narebski's message of "Sun, 09 Mar 2008 01:37:54 -0800 (PST)")

* Jakub Narebski:

>> Has this already been implemented? "git rebase --interactive" comes
>> close, I think.  But minimizing the changes to individual patches seems
>> a bit of work.
>
> You can try to use one of two Git patch management interfaces: 
> StGit or Guilt.

I had missed that StGit has got three-way merge support.  Fortunately,
the need to manage patch sequences has gone away for the time being
(someone else did it for me 8-).  But I'll report back when the need
finally arises.  Thanks.

      reply	other threads:[~2008-03-16 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09  9:30 Editing patch sequences Florian Weimer
2008-03-09  9:37 ` Jakub Narebski
2008-03-16 11:02   ` Florian Weimer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r6eb0w4g.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.