git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 05/10] builtin-fsck: move common object checking code to fsck.c
Date: Tue, 26 Feb 2008 01:19:51 -0800	[thread overview]
Message-ID: <7vskzg6pmw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 12039765002397-git-send-email-mkoegler@auto.tuwien.ac.at

Is this series an unadjusted resend or something?  This particular one
had funny interaction with your own d4fe07f (git-fsck: report missing
author/commit line in a commit as an error) that is already in
'master', so I had to munge it by hand.  It was not so pleasant
(a large chunk of code was moved from builtin-fsck.c to fsck.c),
but that is what the maintainer does, so it's Ok.  But I'd like
you to eyeball the result to see if it looks sane.

I'll push it out as part of 'pu'.  The tip of your topic is
154a955 (receive-pack: use strict mode for unpacking objects)
tonight:

	Side note: To find a tip of a topic yourself, look for "Merge
	mk/maint-parse-careful" in "git log --first-parent
	origin/next..origin/pu" output and find the latest one.

One thing I noticed was that parse_$type_buffer() family all take
non-const void *buf pointers but one new caller you introduced takes
"const void *data" and passes that pointer to them.  I hated to, but
ended up loose-casting it.  You may want to make the function take
non-const pointer, but I did not look very carefully.

By the way, while I was at it, many stylistic issues bugged me too
much, so I ended up fixing them as well:

 * Trailing whitespaces; avoid them.

 * Indenting with SP not HT; don't.

 * Pointer to struct foo type is (struct foo *), not (struct foo*);

 * One SP each around comparison operator "==";

 * One SP around assignment operator "=";

 * One SP after "if", "while", "switch" and friends before "(";

 * No SP between function name and "(";

 * A function without parameter is "static void foo(void)", not
   "static void foo()";

 * Decl-after-statement; don't.

 * Multi-line comment is:

	/*
         * This is multi line comment
         * and this is its second line.
         */

   not

	/* This is multi line comment
           and this is its second */

 * If you cast, cast to the right type ;-)

	struct tree *item = (struct tree *) obj;

   not

	struct tree *item = (struct item*) obj;

Please do not make me do this again, as I do not have infinite amount
of time.  This plea is not only about your patch but applies to
everybody.

I wanted to merge a few new commits to existing topics to 'next' and
merge down a few well cooked topics to 'master', but ran out of time
tonight.  New stuff I received and looked at are all parked in 'pu'
tonight.

  parent reply	other threads:[~2008-02-26  9:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 21:54 [PATCH 01/10] add generic, type aware object chain walker Martin Koegler
2008-02-25 21:54 ` [PATCH 02/10] builtin-fsck: move away from object-refs to fsck_walk Martin Koegler
2008-02-25 21:54   ` [PATCH 03/10] Remove unused object-ref code Martin Koegler
2008-02-25 21:54     ` [PATCH 04/10] builtin-fsck: reports missing parent commits Martin Koegler
2008-02-25 21:54       ` [PATCH 05/10] builtin-fsck: move common object checking code to fsck.c Martin Koegler
2008-02-25 21:54         ` [PATCH 06/10] add common fsck error printing function Martin Koegler
2008-02-25 21:54           ` [PATCH 07/10] unpack-object: cache for non written objects Martin Koegler
2008-02-25 21:54             ` [PATCH 08/10] unpack-objects: prevent writing of inconsistent objects Martin Koegler
2008-02-25 21:54               ` [PATCH 09/10] index-pack: introduce checking mode Martin Koegler
2008-02-25 21:55                 ` [PATCH 10/10] receive-pack: use strict mode for unpacking objects Martin Koegler
2008-02-26  9:19         ` Junio C Hamano [this message]
2008-02-26 21:35           ` [PATCH 05/10] builtin-fsck: move common object checking code to fsck.c Martin Koegler
2008-02-27  7:48             ` 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=7vskzg6pmw.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mkoegler@auto.tuwien.ac.at \
    /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).