From: Christian Couder <christian.couder@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Stephan Beyer <s-beyer@gmx.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH 1/3] sequencer: add "reset_almost_hard()" and related functions
Date: Tue, 4 Aug 2009 15:03:11 +0200 [thread overview]
Message-ID: <c07716ae0908040603t12daa900l18178770a17780b1@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0908041443310.8306@pacific.mpi-cbg.de>
Hi,
On Tue, Aug 4, 2009 at 2:45 PM, Johannes
Schindelin<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 3 Aug 2009, Christian Couder wrote:
>
>> diff --git a/builtin-sequencer--helper.c b/builtin-sequencer--helper.c
>> index 1dda525..82a830d 100644
>> --- a/builtin-sequencer--helper.c
>> +++ b/builtin-sequencer--helper.c
>> @@ -2,16 +2,95 @@
>
> I do not have that file in my tree. Yet your 1/3 already expects it to be
> there.
This file is in pu. One of my previous patch added it.
> Well, I guess I will work on finishing my rebase-i-p branch next week, and
> then see what is there in Stephan's repository, and ask him why he went so
> silent (after all, his code should have been polished enough to be
> included 11 months ago).
Stephan started to work again on his repository a few days ago. He
integrated some of the changes I posted to this list and some
information about what is left to do to complete his work. That will
make it easier for me or anyone who wants to work on this. Thanks
Stephan!
Best regards,
Christian.
prev parent reply other threads:[~2009-08-04 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 2:40 [PATCH 1/3] sequencer: add "reset_almost_hard()" and related functions Christian Couder
2009-08-04 12:45 ` Johannes Schindelin
2009-08-04 13:03 ` Christian Couder [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=c07716ae0908040603t12daa900l18178770a17780b1@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).