From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2010, #02; Wed, 14)
Date: Thu, 15 Jul 2010 13:58:22 +0200 [thread overview]
Message-ID: <20100715115822.GD22574@debian> (raw)
In-Reply-To: <7vhbk1wt8k.fsf@alter.siamese.dyndns.org>
Hi Junio,
Junio C Hamano writes:
> * rr/svn-export (2010-06-10) 7 commits
> - Add LICENSE
> - Add SVN dump parser
> - Add infrastructure to write revisions in fast-export format
> - Add stream helper library
> - Add library for string-specific memory pool
> - Add cpp macro implementation of treaps
> - Add memory pool library
>
> I recall there was another round of re-roll planned for this one.
I was waiting for the ternary treap refactor, but I figure that it's
taking longer than I expected. I'll try to re-roll today.
-- Ram
prev parent reply other threads:[~2010-07-15 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 23:15 What's cooking in git.git (Jul 2010, #02; Wed, 14) Junio C Hamano
2010-07-15 11:58 ` Ramkumar Ramachandra [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=20100715115822.GD22574@debian \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).