From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2009, #05; Wed, 28)
Date: Wed, 28 Oct 2009 15:09:22 -0700 [thread overview]
Message-ID: <fabb9a1e0910281509r1c88615y7dc85e529ac032f3@mail.gmail.com> (raw)
In-Reply-To: <7vfx93jkb1.fsf@alter.siamese.dyndns.org>
Heya,
On Wed, Oct 28, 2009 at 14:11, Junio C Hamano <gitster@pobox.com> wrote:
> * sr/gfi-options (2009-09-06) 6 commits.
> - fast-import: test the new option command
> - fast-import: add option command
> - fast-import: test the new feature command
> - fast-import: add feature command
> - fast-import: put marks reading in it's own function
> - fast-import: put option parsing code in separate functions
>
> ???
Repinged Shawn and the vcs list to decide what to do, I really want to
get this done with...
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-10-28 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 21:11 What's cooking in git.git (Oct 2009, #05; Wed, 28) Junio C Hamano
2009-10-28 22:09 ` Sverre Rabbelier [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=fabb9a1e0910281509r1c88615y7dc85e529ac032f3@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).