From: "Ping Yin" <pkufranky@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin-commit: Fix git-commit honoring status.color
Date: Tue, 20 Nov 2007 02:26:59 +0800 [thread overview]
Message-ID: <46dff0320711191026l6d749886y4fd3879f555c6107@mail.gmail.com> (raw)
In-Reply-To: <7vejenuy4i.fsf@gitster.siamese.dyndns.org>
>
> Although I admit I do not care much about the "status color", I
> suspect this patch is not quite right.
>
> When prepare_log_message() returns "no committable changes" and
> we are not in merge, the calling cmd_commit() does another
> run_status() to show the status of the index and the work tree
> to the stdout, and at that point, we _do_ want to honor the
> configuration setting you are discarding with this assignment.
>
You're right. I forgot about untracked files when there are 'no
committable changes'
> ---
>
> builtin-commit.c | 5 ++++-
> wt-status.h | 1 +
> 2 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/builtin-commit.c b/builtin-commit.c
> index 4e2f4aa..058cd32 100644
> --- a/builtin-commit.c
> +++ b/builtin-commit.c
> @@ -300,7 +300,7 @@ static const char sign_off_header[] = "Signed-off-by: ";
> static int prepare_log_message(const char *index_file, const char *prefix)
> {
> struct stat statbuf;
> - int commitable;
> + int commitable, saved_color_setting;
> struct strbuf sb;
> char *buffer;
> FILE *fp;
> @@ -383,7 +383,10 @@ static int prepare_log_message(const char *index_file, const char *prefix)
> if (only_include_assumed)
> fprintf(fp, "# %s\n", only_include_assumed);
>
> + saved_color_setting = wt_status_use_color;
> + wt_status_use_color = 0;
> commitable = run_status(fp, index_file, prefix);
> + wt_status_use_color = saved_color_setting;
>
> fclose(fp);
>
> diff --git a/wt-status.h b/wt-status.h
> index f58ebcb..225fb4d 100644
> --- a/wt-status.h
> +++ b/wt-status.h
> @@ -27,6 +27,7 @@ struct wt_status {
> };
>
> int git_status_config(const char *var, const char *value);
> +int wt_status_use_color;
> void wt_status_prepare(struct wt_status *s);
> void wt_status_print(struct wt_status *s);
>
>
--
Ping Yin
prev parent reply other threads:[~2007-11-19 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 17:10 [PATCH] builtin-commit: Fix git-commit honoring status.color Ping Yin
2007-11-18 19:55 ` Junio C Hamano
2007-11-18 20:30 ` [PATCH] builtin-commit: run commit-msg hook with correct message file Junio C Hamano
2007-11-19 18:26 ` Ping Yin [this message]
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=46dff0320711191026l6d749886y4fd3879f555c6107@mail.gmail.com \
--to=pkufranky@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).