From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git List <git@vger.kernel.org>,
Ian Clatworthy <ian.cla
Subject: [PATCH v5a 0/6] add new feature and option command
Date: Thu, 27 Aug 2009 11:40:25 -0700 [thread overview]
Message-ID: <1251398431-12461-1-git-send-email-srabbelier@gmail.com> (raw)
Apologies for the borked v5.
This is a reroll of sr/gfi-options to include suggestions from an
off-list discussion about the fast-import format.
Reworked the series (compared to v4) to introduce a 'feature' command
first, and use that in the new 'option' series.
Sverre Rabbelier (6):
fast-import: put option parsing code in seperate functions
fast-import: put marks reading in it's own function
fast-import: add feature command
fast-import: test the new feature command
fast-import: add option command
fast-import: test the new option command
Documentation/git-fast-import.txt | 39 ++++++
fast-import.c | 255 ++++++++++++++++++++++++++-----------
t/t9300-fast-import.sh | 86 +++++++++++++
3 files changed, 303 insertions(+), 77 deletions(-)
next reply other threads:[~2009-08-27 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 18:40 Sverre Rabbelier [this message]
2009-08-27 18:40 ` [PATCH v5a 1/6] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-27 18:40 ` [PATCH v5a 2/6] fast-import: put marks reading in it's own function Sverre Rabbelier
2009-08-27 18:40 ` [RFC PATCH v5a 3/6] fast-import: add feature command Sverre Rabbelier
2009-08-27 18:40 ` [RFC PATCH v5a 4/6] fast-import: test the new " Sverre Rabbelier
2009-08-27 18:40 ` [PATCH v5a 5/6] fast-import: add option command Sverre Rabbelier
2009-08-27 18:40 ` [PATCH v5a 6/6] fast-import: test the new " Sverre Rabbelier
2009-08-27 18:52 ` [PATCH v5a 1/6] fast-import: put option parsing code in seperate functions Teemu Likonen
2009-08-27 19:37 ` Sverre Rabbelier
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=1251398431-12461-1-git-send-email-srabbelier@gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.