All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Improve git-prune -n output
Date: Thu, 26 Oct 2006 18:37:23 +0100	[thread overview]
Message-ID: <200610261837.31356.andyparkins@gmail.com> (raw)
In-Reply-To: <7vlkn3kn65.fsf@assigned-by-dhcp.cox.net>

On Thursday 2006, October 26 18:21, Junio C Hamano wrote:

> I do not have an objection to what this does, except I wonder if
> somebody's script relies on parsing this output already.

I did think of that, but the existing output looked pretty non-useful for easy 
parsing because of the fact that filenames where being printed instead of 
hashes.  If I were given free reign I think I'd want to drop the "would 
prune" message as well.

> It is customary to have one empty line before the S-o-b: line.

I didn't do it.  Git did :-)  I'll keep an eye out for it from now on.  
Apologies (as usual)


Andy
-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE

  reply	other threads:[~2006-10-26 17:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 10:38 [PATCH] Improve git-prune -n output Andy Parkins
2006-10-26 17:21 ` Junio C Hamano
2006-10-26 17:37   ` Andy Parkins [this message]
2006-10-27  8:37   ` Andy Parkins
2006-10-28 14:00     ` Jakub Narebski
2006-10-28 20:37       ` Junio C Hamano
2006-10-26 17:33 ` Andy Whitcroft
2006-10-27  1:45   ` Petr Baudis
2006-10-27  8:19   ` Andy Parkins
2006-10-27  9:09     ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2006-11-02 11:12 Andy Parkins
2006-11-03  2:40 ` 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=200610261837.31356.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.