From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, sverre@rabbelier.nl
Subject: Re: What's cooking in git.git (Aug 2009, #05; Wed, 26)
Date: Wed, 26 Aug 2009 16:49:03 -0700 [thread overview]
Message-ID: <20090826234903.GR1033@spearce.org> (raw)
In-Reply-To: <7vfxbeb0mt.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> * sr/gfi-options (2009-08-24) 4 commits
> - fast-import: test the new option command
> - fast-import: add option command
> - fast-import: put marks reading in it's own function
> - fast-import: put option parsing code in seperate functions
>
> Will merge to 'next' shortly.
Please don't.
There is an off-git ML thread running between the various DVCS
tool developers who work on the fast-import/fast-export tools for
the respective DVCSes. In that thread we have decided to slightly
change this grammar and this series needs to be respun.
If you are itching to do something, eject it from pu and wait for
the respin.
--
Shawn.
next prev parent reply other threads:[~2009-08-26 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 23:45 What's cooking in git.git (Aug 2009, #05; Wed, 26) Junio C Hamano
2009-08-26 23:49 ` Shawn O. Pearce [this message]
2009-08-27 0:10 ` Sverre Rabbelier
2009-08-27 0:12 ` Shawn O. Pearce
2009-08-27 19:48 ` Sverre Rabbelier
2009-08-27 16:41 ` Brandon Casey
2009-08-27 17:32 ` Junio C Hamano
2009-08-27 18:02 ` Brandon Casey
2009-08-28 22:32 ` [PATCH master] t/test-lib.sh: provide a shell implementation of the 'yes' utility Brandon Casey
2009-08-30 1:46 ` What's cooking in git.git (Aug 2009, #05; Wed, 26) Daniel Barkalow
2009-08-30 4:06 ` Junio C Hamano
2009-08-30 20:31 ` Junio C Hamano
2009-08-31 17:06 ` Daniel Barkalow
2009-08-31 23:35 ` Junio C Hamano
2009-09-01 4:18 ` Daniel Barkalow
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=20090826234903.GR1033@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
/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).