From: Petr Baudis <pasky@ucw.cz>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Misc fixes for git-pasky
Date: Fri, 15 Apr 2005 00:49:34 +0200 [thread overview]
Message-ID: <20050414224934.GO22699@pasky.ji.cz> (raw)
In-Reply-To: <1113518277.8609.8.camel@dv>
Dear diary, on Fri, Apr 15, 2005 at 12:37:57AM CEST, I got a letter
where Pavel Roskin <proski@gnu.org> told me that...
> Hi, Petr!
>
> The attached patch against current git-pasky does following:
Hum. It does too much at once, that means I cannot apply it easily. :-(
> * README: spell checked
Good. :-)
> * cache.h: Include unistd.h. Needed for close() definition. While
> current zlib.h header includes unistd.h, it's not guaranteed to be so in
> other zlib versions.
Sounds good.
> * read-cache.c: Avoid C++ comments. C comments are more readable for C
> programmers. Besides, we don't want git to be so unportable that "gcc
> -pedantic" cannot compile it.
I don't really care about this too much, although I personally prefer
the old-style comments. // comments are C99 so -pedantic by itself
should have no right to complain about it.
> * show-diff.c: Fix handling of more than one option of the command line.
What exactly does it fix? The current code seems fine to my sleepy
brain.
> Add new option "-c" to omit checksums for modified files. Expand help.
How is the -c option useful?
Could you please send your patch with the correct inline settings on the
attachment (or just in the mail body) and signed off?
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
parent reply other threads:[~2005-04-14 22:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1113518277.8609.8.camel@dv>]
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=20050414224934.GO22699@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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