From: Stephan Beyer <s-beyer@gmx.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: rebase--interactive in C vs. sequencer
Date: Sat, 5 Apr 2008 14:22:30 +0200 [thread overview]
Message-ID: <20080405122230.GC14565@leksak.fem-net> (raw)
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hi Daniel,
in [1] you have told that you are working on porting rebase--interactive
to the C programming language. In reply, Junio pointed out that a
consolidated "git sequencer" is desired.
The sequencer became a project idea for Google Summer of Code and I am
currently applying for that project. But I had your mail in mind and
do not want that any work of yours is thrown away. ;-)
So... what is the current state?
Are you still working on it?
Is there a code stub or even more code which could be used for the
sequencer task?
Regards,
Stephan
References:
1. http://marc.info/?l=git&m=120327576215702
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-04-05 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 12:22 Stephan Beyer [this message]
2008-04-06 21:44 ` rebase--interactive in C vs. sequencer Daniel Barkalow
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=20080405122230.GC14565@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=barkalow@iabervon.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox