From: "Kristian Høgsberg" <krh@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] This exports the update() function from builtin-add.c as
Date: Wed, 03 Oct 2007 18:03:54 -0400 [thread overview]
Message-ID: <1191449034.7134.19.camel@hinata.boston.redhat.com> (raw)
In-Reply-To: <7v7imcv5op.fsf@gitster.siamese.dyndns.org>
On Thu, 2007-09-27 at 02:05 -0700, Junio C Hamano wrote:
...
> I think the right organization for the "builtin-commit" series
> should be:
>
> * merge strbuf topic in kh/commit topic, in order to get the
> stripspace updates and strbuf_read_file();
>
> * add--interactive entry point change (respin the one from the
> old series);
>
> * rename update() to add_files_to_cache() and export (respin
> this [2/4] with a better commit message);
>
> * create a separate rerere() function and export (respin part
> of old series, with proper refactoring);
>
> I am not happy with builtin-foo.c calling into something from
> builtin-bar.c, though. We probably would want to move
> rerere() and add_files_to_cache() somewhere else.
>
> * move launch_editor() and stripspace() to create editor.c (new
> [4/4]);
>
> * add option parser in parse-options.[ch] (new [1/4]);
>
> * finally, create builtin-commit that uses the groundwork laid
> out above (new [3/4]).
>
> I ended up doing the above up to the rerere() one myself, but
> haven't done the rest.
>From what I see in next today, it looks like we're just missing the
parse-options patch and builtin-commit patches. I resent a better
version of parse-options and a patch that ports builtin-add.c to the
option parser. To use the option parser in more places, we'll probably
have to extend it a bit, but the patch is a good start. Let's get that
in shape and into next and then I'll send an updated builtin-commit
patch.
thanks,
Kristian
next prev parent reply other threads:[~2007-10-03 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 4:50 [PATCH 1/4] Add a simple option parser for use by builtin-commit.c Kristian Høgsberg
2007-09-27 4:50 ` [PATCH 2/4] This exports the update() function from builtin-add.c as Kristian Høgsberg
2007-09-27 4:50 ` [PATCH 3/4] Implement git commit as a builtin command Kristian Høgsberg
2007-09-27 4:50 ` [PATCH 4/4] Move launch_editor() and stripspace() to new file editor.c Kristian Høgsberg
2007-09-27 9:05 ` [PATCH 2/4] This exports the update() function from builtin-add.c as Junio C Hamano
2007-10-03 22:03 ` Kristian Høgsberg [this message]
2007-09-27 11:47 ` Johannes Schindelin
2007-09-27 19:50 ` Junio C Hamano
2007-09-30 13:11 ` [PATCH 1/4] Add a simple option parser for use by builtin-commit.c Jonas Fonseca
2007-10-01 10:14 ` Johannes Schindelin
2007-10-01 10:31 ` Jonas Fonseca
2007-10-01 11:39 ` Johannes Schindelin
2007-10-01 15:00 ` Jeff King
2007-10-01 16:26 ` Kristian Høgsberg
2007-10-01 18:13 ` Johannes Schindelin
2007-10-03 20:11 ` Jonas Fonseca
2007-10-03 21:53 ` Kristian Høgsberg
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=1191449034.7134.19.camel@hinata.boston.redhat.com \
--to=krh@redhat.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).