git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Alex Riesen <raa.lkml@gmail.com>,
	Constantine Plotnikov <constantine.plotnikov@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Implement git clone -v
Date: Thu, 09 Oct 2008 04:06:40 -0700	[thread overview]
Message-ID: <7vr66qown3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1223509232-3520-1-git-send-email-vmiklos@frugalware.org> (Miklos Vajna's message of "Thu, 9 Oct 2008 01:40:32 +0200")

Miklos Vajna <vmiklos@frugalware.org> writes:

> The new -v option forces the progressbar, even in case the output is not
> a terminal.
>
> Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>

The patch made me wonder why this new feature had to be implemented in the
first place and had me look up the message the patch was an follow-up to.
For somebody who would not recall the original request-for-feature (that
includes you 6 months from now), it would have been easier to understand
the context if the commit message said what the intended purpose of this
(i.e. "have it read by an IDE").

  reply	other threads:[~2008-10-09 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 20:01 Forcing progerss output for clone Constantine Plotnikov
2008-10-04 21:42 ` Alex Riesen
2008-10-06 22:19   ` [PATCH] Implement git clone -v Miklos Vajna
2008-10-07  6:21     ` Alex Riesen
2008-10-07 19:39       ` Miklos Vajna
2008-10-08  6:02         ` Shawn O. Pearce
2008-10-08  6:25           ` Alex Riesen
2008-10-08 23:40           ` Miklos Vajna
2008-10-09 11:06             ` Junio C Hamano [this message]
2008-10-09 15:20               ` Shawn O. Pearce
2008-10-09 21:26                 ` Miklos Vajna

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=7vr66qown3.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=constantine.plotnikov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    --cc=spearce@spearce.org \
    --cc=vmiklos@frugalware.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;
as well as URLs for NNTP newsgroup(s).