From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stephan Beyer <s-beyer@gmx.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH 00/13] more changes to port rebase -i to C using sequencer code
Date: Wed, 12 Aug 2009 14:49:10 -0700 [thread overview]
Message-ID: <7vljlowvmx.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20090812051116.18155.70541.chriscool@tuxfamily.org> (Christian Couder's message of "Wed\, 12 Aug 2009 07\:15\:38 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> These is just the current state of my work.
> Some patches have already been sent but are not yet in pu.
It seems that some later patches in the series are "oops, the earlier one
made mistakes and this patch fixes them". Could you fix them where they
were introduced?
prev parent reply other threads:[~2009-08-12 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 5:15 [PATCH 00/13] more changes to port rebase -i to C using sequencer code Christian Couder
2009-08-12 5:15 ` [PATCH 01/13] sequencer: add "do_fast_forward()" to perform a fast forward Christian Couder
2009-08-12 5:15 ` [PATCH 02/13] sequencer: add "--fast-forward" option to "git sequencer--helper" Christian Couder
2009-08-12 5:15 ` [PATCH 03/13] sequencer: let "git sequencer--helper" callers set "allow_dirty" Christian Couder
2009-08-12 5:15 ` [PATCH 04/13] rebase -i: use "git sequencer--helper --fast-forward" Christian Couder
2009-08-12 5:15 ` [PATCH 05/13] revert: libify pick Christian Couder
2009-08-12 5:15 ` [PATCH 06/13] pick: simplify "error(...)" followed by "return -1" Christian Couder
2009-08-12 5:15 ` [PATCH 07/13] pick: rename "pick()" to "pick_commit()" Christian Couder
2009-08-12 5:15 ` [PATCH 08/13] pick: remove useless PICK_REVERSE => PICK_ADD_NOTE code Christian Couder
2009-08-12 5:15 ` [PATCH 09/13] pick: simplify bogus comment about commiting immediately Christian Couder
2009-08-12 5:15 ` [PATCH 10/13] pick: libify "pick_help_msg()" Christian Couder
2009-08-12 5:15 ` [PATCH 11/13] sequencer: add "do_commit()" and related functions Christian Couder
2009-08-12 5:15 ` [PATCH 12/13] sequencer: add "--cherry-pick" option to "git sequencer--helper" Christian Couder
2009-08-12 5:15 ` [PATCH 13/13] rebase -i: use "git sequencer--helper --cherry-pick" Christian Couder
2009-08-12 21:49 ` Junio C Hamano [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=7vljlowvmx.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=s-beyer@gmx.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox