All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Yuxuan Shui <yshuiv7@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 1/2] fsck.c: Change the type of fsck_ident()'s first argument
Date: Thu, 13 Mar 2014 12:11:03 -0700	[thread overview]
Message-ID: <xmqqbnx9j4mw.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1394685951-9726-2-git-send-email-yshuiv7@gmail.com> (Yuxuan Shui's message of "Thu, 13 Mar 2014 12:45:50 +0800")

Yuxuan Shui <yshuiv7@gmail.com> writes:

> Since fsck_ident doesn't change the content of **ident, the type of
> ident could be const char **.
>
> This change is required to rewrite fsck_commit() to use skip_prefix().
>
> Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
> ---

It may not be a bad idea to read and understand reviews other people
are receiving for their microprojects, e.g. $gmane/243852.

"Change the type" is not technically incorrect per-se, but when
viewed in "git shortlog" output, it wastes more bytes than it
conveys information about this change if stated differently.  Any
patch that touch existing code is a "change" by definition.

Perhaps

	fsck.c:fsck_ident(): ident argument points at a const string

or something?

I see that the body of the patch follows the review by Peff on the
previous round of this series, so I'll forge a Helped-by: or
something into the log message when I queue this patch.

Thanks.

>  fsck.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fsck.c b/fsck.c
> index 99c0497..7776660 100644
> --- a/fsck.c
> +++ b/fsck.c
> @@ -243,7 +243,7 @@ static int fsck_tree(struct tree *item, int strict, fsck_error error_func)
>  	return retval;
>  }
>  
> -static int fsck_ident(char **ident, struct object *obj, fsck_error error_func)
> +static int fsck_ident(const char **ident, struct object *obj, fsck_error error_func)
>  {
>  	if (**ident == '<')
>  		return error_func(obj, FSCK_ERROR, "invalid author/committer line - missing space before email");
> @@ -281,7 +281,7 @@ static int fsck_ident(char **ident, struct object *obj, fsck_error error_func)
>  
>  static int fsck_commit(struct commit *commit, fsck_error error_func)
>  {
> -	char *buffer = commit->buffer;
> +	const char *buffer = commit->buffer;
>  	unsigned char tree_sha1[20], sha1[20];
>  	struct commit_graft *graft;
>  	int parents = 0;

  reply	other threads:[~2014-03-13 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  4:45 [PATCH v3 0/2] GSoC micro project, rewrite fsck_commit() to use skip_prefix() Yuxuan Shui
2014-03-13  4:45 ` [PATCH v3 1/2] fsck.c: Change the type of fsck_ident()'s first argument Yuxuan Shui
2014-03-13 19:11   ` Junio C Hamano [this message]
2014-03-13  4:45 ` [PATCH v3 2/2] fsck.c: Rewrite fsck_commit() to use skip_prefix() Yuxuan Shui
2014-03-13 19:14   ` Junio C Hamano
2014-03-13 19:42     ` Junio C Hamano

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=xmqqbnx9j4mw.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=yshuiv7@gmail.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 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.