git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristian Høgsberg" <krh@redhat.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 7/7] Implement git commit as a builtin command.
Date: Tue, 18 Sep 2007 11:07:32 -0400	[thread overview]
Message-ID: <1190128052.23692.6.camel@hinata.boston.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709181453220.28586@racer.site>

On Tue, 2007-09-18 at 14:58 +0100, Johannes Schindelin wrote:
> Hi,
> 
> very nice!
> 
> Four nits, though, and a half:
> 
> - it would be nicer to put the option parsing it option.[ch] (you would 
>   also need to pass the usage line then, instead of hardwiring it to 
>   "git_commit_usage"),

Yes, good point.

> - it seems more logical to me to call it "parse_option()" than 
>   "scan_options()", since that is what it does,

Yup.

> - you might want to rename OPTION_NONE to OPTION_BOOLEAN, and maybe even 
>   allow "--no-<option>" in that case for free,

Agree.

> - wt_status_prepare() could take a parameter "index_file", which would 
>   default to git_path("index") when passed as NULL, and

Yeah, the way I did it, I preserved the API, but that's not really a
concern, I guess.

> - launch_editor() is defined in builtin-tag.c, which is not part of the 
>   library, and therefore it would be technically more correct to either 
>   move the function to editor.c (my preferred solution), or declare it in 
>   builtin.h instead of strbuf.h.

Yeah, and we should move the stripspace code there too.  Or maybe we
should rename that strbuf_stripspace and put it in strbuf.c.

> As you can see, my nits are really minor, which means that I am pretty 
> happy with your work!

Great, I hope we can get it in soon :)

Kristian

  reply	other threads:[~2007-09-18 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  0:06 [PATCH 1/7] Enable wt-status output to a given FILE pointer Kristian Høgsberg
2007-09-18  0:06 ` [PATCH 2/7] Enable wt-status to run against non-standard index file Kristian Høgsberg
2007-09-18  0:06   ` [PATCH 3/7] Introduce entry point for launching add--interactive Kristian Høgsberg
2007-09-18  0:06     ` [PATCH 4/7] Clean up stripspace a bit, use strbuf even more Kristian Høgsberg
2007-09-18  0:06       ` [PATCH 5/7] Add strbuf_read_file() Kristian Høgsberg
2007-09-18  0:06         ` [PATCH 6/7] Export rerere() and launch_editor() Kristian Høgsberg
2007-09-18  0:06           ` [PATCH 7/7] Implement git commit as a builtin command Kristian Høgsberg
2007-09-18 13:58             ` Johannes Schindelin
2007-09-18 15:07               ` Kristian Høgsberg [this message]
2007-09-20  1:27             ` Junio C Hamano
2007-09-21 17:18               ` Kristian Høgsberg
2007-09-21 19:32                 ` Junio C Hamano
2007-09-24 20:27                   ` Kristian Høgsberg
2007-09-18 13:14           ` [PATCH 6/7] Export rerere() and launch_editor() Johannes Schindelin
2007-09-19 23:52           ` Junio C Hamano
2007-09-21 18:01             ` Kristian Høgsberg
2007-09-18 13:12       ` [PATCH 4/7] Clean up stripspace a bit, use strbuf even more Johannes Schindelin
2007-09-18 13:52         ` 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=1190128052.23692.6.camel@hinata.boston.redhat.com \
    --to=krh@redhat.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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).