From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
Jeff King <peff@peff.net>
Subject: [GSoC update] Sequencer: Iterating over a stable series
Date: Tue, 7 Jun 2011 11:18:50 +0530 [thread overview]
Message-ID: <BANLkTik93BB7p0gNMx5ZfsSCjietXxiG3w@mail.gmail.com> (raw)
Hi,
I will start posting weekly updates starting with this one, since I
now have quite a lot to say :) Over the first few weeks, my objective
was to keep iterating the initial series I'd posted until I ended up
with a more-or-less acceptable version. This [1] doesn't seem far
away. Now, I'm busy writing some tests, and planning out the
functionality of each of the individual features -- as soon as I
understand the problem correctly (see discussions in [2] and [3]), I
will start working on writing new features. I'm quite hopeful about
meeting my mid-term target. Please feel free to email me any
comments/ queries about this project. Alternatively, catch me on
#git-devel on Freenode IRC; I'm almost always available, except when
I'm sleeping.
Jeff: I was out of town these last few days. I saw your email about
the lockfile API confusion- will investigate and comment soon.
As usual, the latest code can be found on the sequencer branch of my
GitHub fork [4].
Thanks for reading!
-- Ram
[1]: http://thread.gmane.org/gmane.comp.version-control.git/174526
[2]: http://thread.gmane.org/gmane.comp.version-control.git/174393/focus=174945
[3]: http://thread.gmane.org/gmane.comp.version-control.git/174874
[4]: http://github.com/artagnon/git
next reply other threads:[~2011-06-07 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 5:48 Ramkumar Ramachandra [this message]
2011-06-07 11:32 ` [GSoC update] Sequencer: Iterating over a stable series Christian Couder
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=BANLkTik93BB7p0gNMx5ZfsSCjietXxiG3w@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.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).