From: Jakub Narebski <jnareb@gmail.com>
To: Christian Jaeger <chrjae@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE/RFC] cj-git-patchtool: a "rebase -i" with more interaction
Date: Wed, 03 Aug 2011 03:55:21 -0700 (PDT) [thread overview]
Message-ID: <m3d3gmrchz.fsf@localhost.localdomain> (raw)
In-Reply-To: <CAEjYwfUY9tF_9frkaS7Aw26CPJA02Cr3HDN5Qpkup1rfHYacXw@mail.gmail.com>
Christian Jaeger <chrjae@gmail.com> writes:
> So I've written a set of tools[1] that separates the acts of editing
> and applying history changes.
[...]
>
> For more information see the README on Github.[1]
[...]
I have added cj-git-patchtool to "Patch-management Interface layers"
section of "Interfaces, frontends and tools" page on Git Wiki:
https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#cj-git-patchtool
Please check if it is correct, and improve project description if
needed.
> I don't know whether there are other tools offering the same now.
> Also, I have written this "just for myself", and for this reason made
> use of a set of never-before released Perl libraries of mine. If
> there's general interest in this tool, I'll be glad to help get rid of
> the dependency on these libraries (or clean them up and publish them
> properly, too).
I use one of patch management interfaces for that, namely StGit. It
operates on stack of patches, which you can apply and unapply, going
back and forth and correcting them.
--
Jakub Narębski
next prev parent reply other threads:[~2011-08-03 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 19:22 [ANNOUNCE/RFC] cj-git-patchtool: a "rebase -i" with more interaction Christian Jaeger
2011-08-03 10:55 ` Jakub Narebski [this message]
2011-08-04 6:02 ` Christian Jaeger
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=m3d3gmrchz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=chrjae@gmail.com \
--cc=git@vger.kernel.org \
/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.