From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: Tuncer Ayaz <tuncer.ayaz@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Teach/Fix pull/fetch -q/-v options
Date: Mon, 27 Oct 2008 20:21:35 -0700 [thread overview]
Message-ID: <7vprllh0ao.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081027190816.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Mon, 27 Oct 2008 19:08:16 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> Quoting Tuncer Ayaz <tuncer.ayaz@gmail.com>:
>
>> After fixing clone -q I noticed that pull -q does not do what
>> it's supposed to do and implemented --quiet/--verbose by
>> adding it to builtin-merge and fixing two places in builtin-fetch.
>
> Junio, may I ask what the status of this patch is? Maybe the patch was lost in the noise? The commit log message is written very differently from existing commits in the history of git, and I am thinking that maybe that is why you did not like the whole patch? Or is it lack of any test script?
Well, perhaps you've been with us long enough to get too picky like
myself, but this was genuinely lost in the noise and my scrambling to get
back to normal. We do not typically say "I did this, I did that", but the
first paragraph in Tuncer's message is perfectly fine. I would probably
liked the second paragraph better if it were after --- lines (it is more
about the possible enhancements in other areas, and does not belong to the
commit log message for this change), but it is not a grave enough offence
to get the patch rejected.
The patch itself looks Ok; the lack of test script additions does indeed
bother me somewhat, but it is not too big a deal.
P.S. We are having fun at GitTogether'08 in the first half of this week,
so please expect slower response than usual.
next prev parent reply other threads:[~2008-10-28 3:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:30 [PATCH] Teach/Fix pull/fetch -q/-v options Tuncer Ayaz
2008-10-27 10:08 ` Nanako Shiraishi
2008-10-28 3:21 ` Junio C Hamano [this message]
2008-11-01 17:23 ` Tuncer Ayaz
2008-11-07 3:26 ` Tuncer Ayaz
-- strict thread matches above, loose matches on Subject: below --
2008-11-15 19:23 Tuncer Ayaz
2008-11-17 10:37 ` Tuncer Ayaz
2008-11-17 10:51 ` Junio C Hamano
2008-11-17 10:55 ` Tuncer Ayaz
2008-11-17 11:03 ` Constantine Plotnikov
2008-11-17 22:24 ` Tuncer Ayaz
2008-11-17 22:08 ` Tuncer Ayaz
2008-11-15 0:14 Tuncer Ayaz
2008-11-15 1:15 ` Junio C Hamano
2008-11-15 1:53 ` Tuncer Ayaz
2008-11-15 3:10 ` Junio C Hamano
2008-11-15 17:28 ` Tuncer Ayaz
2008-11-15 17:42 ` Tuncer Ayaz
2008-11-15 19:16 ` Tuncer Ayaz
2008-11-07 3:26 Tuncer Ayaz
2008-11-10 23:43 ` Tuncer Ayaz
2008-11-12 20:47 ` Junio C Hamano
2008-11-15 0:09 ` Tuncer Ayaz
2008-10-20 16:28 Tuncer Ayaz
2008-10-19 19:48 Tuncer Ayaz
2008-10-19 21:26 ` Junio C Hamano
2008-10-20 16:35 ` Tuncer Ayaz
2008-10-20 23:54 ` Junio C Hamano
2008-10-21 16:25 ` Tuncer Ayaz
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=7vprllh0ao.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
--cc=tuncer.ayaz@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 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).