From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2009, #02; Sun, 11)
Date: Mon, 12 Oct 2009 08:23:02 +0200 [thread overview]
Message-ID: <fabb9a1e0910112323x35798972qe213025f37af82b3@mail.gmail.com> (raw)
In-Reply-To: <7vfx9pmhae.fsf@alter.siamese.dyndns.org>
Heya,
On Mon, Oct 12, 2009 at 05:18, Junio C Hamano <gitster@pobox.com> wrote:
> [Stalled]
>
> * 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
>
> Ejected from 'next' as fast-import folks still seem to be discussing with
> how to proceed.
Thanks, I hope to have this re-rolled before 1.6.6 goes into RC.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-10-12 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 3:18 What's cooking in git.git (Oct 2009, #02; Sun, 11) Junio C Hamano
2009-10-12 5:14 ` Jeff King
2009-10-12 22:52 ` Junio C Hamano
2009-10-14 4:24 ` Jeff King
2009-10-12 6:23 ` Sverre Rabbelier [this message]
2009-10-14 18:29 ` Jens Lehmann
2009-10-14 18:30 ` [PATCH 1/4] Add the --submodule-summary option to the diff option family Jens Lehmann
2009-10-14 18:31 ` [PATCH 2/4] fix indentation depth for git diff --submodule-summary Jens Lehmann
2009-10-14 18:31 ` [PATCH 3/4] fix output for deleted submodules in " Jens Lehmann
2009-10-14 18:32 ` [PATCH 4/4] add tests for " Jens Lehmann
2009-10-14 20:34 ` submodule-summary Junio C Hamano
2009-10-14 21:27 ` submodule-summary Jens Lehmann
2009-10-14 22:42 ` submodule-summary Junio C Hamano
2009-10-15 10:34 ` submodule-summary Jens Lehmann
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=fabb9a1e0910112323x35798972qe213025f37af82b3@mail.gmail.com \
--to=srabbelier@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).