git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brandon Casey <drafnel@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] prune.c: only print informational message in show_only or verbose mode
Date: Tue, 7 Aug 2012 17:59:46 -0400	[thread overview]
Message-ID: <20120807215946.GB22974@sigill.intra.peff.net> (raw)
In-Reply-To: <7vlihqv0ks.fsf@alter.siamese.dyndns.org>

On Tue, Aug 07, 2012 at 02:44:51PM -0700, Junio C Hamano wrote:

> Ok, so I'll queue it as a separate topic with a different
> justification.
> 
> -- >8 --
> From: Brandon Casey <drafnel@gmail.com>
> Date: Mon, 6 Aug 2012 22:01:49 -0700
> Subject: [PATCH] prune.c: only print informational message in show_only or verbose mode
> 
> "git prune" reports removal of loose object files that are no longer
> necessary only under the "-v" option, but unconditionally reports
> removal of temporary files that are no longer needed.
> 
> The original thinking was that presence of a leftover temporary file

s/presence/the &/

> should be an unusual occurrence that may indicate an earlier failure
> of some sort, and the user may want to be reminded of it.  Removing
> an unnecessary loose object file, on the other hand, is just part of
> the normal operation.  That is why the former is always printed out
> and the latter only when -v is used.
> 
> But neither report is particularly useful.  Hide both of these
> behind the "-v" option for consistency.
> 
> Signed-off-by: Brandon Casey <drafnel@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---

Looks fine to me.  I think tmpfile removal is also not that interesting
in general. A stale file can happen any time the user aborts an
operation via ^C. But I think your justification is sufficient as-is
(and this topic is not worth spending too much more time on).

-Peff

  reply	other threads:[~2012-08-07 21:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05  1:55 Did we break receive-pack recently? Junio C Hamano
2012-08-06  1:37 ` Brandon Casey
2012-08-06  3:32   ` Brandon Casey
2012-08-07  5:01     ` [PATCH 1/2] t/t5400: demonstrate breakage caused by informational message from prune Brandon Casey
2012-08-07  5:01       ` [PATCH 2/2] prune.c: only print informational message in show_only or verbose mode Brandon Casey
2012-08-07  5:28         ` Junio C Hamano
2012-08-07  5:34           ` Junio C Hamano
2012-08-07  5:44             ` Brandon Casey
2012-08-07  6:03               ` Jeff King
2012-08-07  6:33                 ` Brandon Casey
2012-08-07 15:41                   ` Junio C Hamano
2012-08-07 21:44                 ` Junio C Hamano
2012-08-07 21:59                   ` Jeff King [this message]
2012-08-07 22:55                   ` Brandon Casey
2012-08-07  5:32         ` Jeff King

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=20120807215946.GB22974@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=drafnel@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).