From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: [GSoC update] Sequencer --continue in pu
Date: Mon, 27 Jun 2011 21:49:49 +0530 [thread overview]
Message-ID: <BANLkTi=65mpGmpZmb--2im96ABv74-m3kw@mail.gmail.com> (raw)
Hi,
I haven't been able to do much work this week due to travelling and
some other engagements. The latest series [1] is now in 'pu'
(31cd3b18), and should be accessible to a wider audience. I will
hopefully have a nicer series with additional tests ready by the end
of the week. While this cooks, I plan to sketch out some
post-mid-term work as RFC patches before the evaluations.
As usual, feel free to contact me about anything. Thanks for reading.
-- Ram
[1]: http://thread.gmane.org/gmane.comp.version-control.git/176139
reply other threads:[~2011-06-27 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='BANLkTi=65mpGmpZmb--2im96ABv74-m3kw@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/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).