From: Junio C Hamano <gitster@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Julien Danjou <julien@danjou.info>, git@vger.kernel.org
Subject: Re: [PATCH] git-remote: make remote name optional for prune operation
Date: Wed, 06 May 2009 10:54:04 -0700 [thread overview]
Message-ID: <7vr5z2ungj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vab5qw3nr.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 06 May 2009 10\:18\:48 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I think we try to make an opearation that discards information from many
> things at once by mistake, and it feels that this patch goes against it.
Sorry, "by mistake" should have read "harder to trigger by mistake".
next prev parent reply other threads:[~2009-05-06 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 14:37 [PATCH] git-remote: make remote name optional for prune operation Julien Danjou
2009-05-06 14:49 ` Francis Galiegue
2009-05-06 15:32 ` Julien Danjou
2009-05-06 15:46 ` Jacob Helwig
2009-05-06 16:15 ` Michael J Gruber
2009-05-06 16:58 ` Julien Danjou
2009-05-06 17:18 ` Junio C Hamano
2009-05-06 17:54 ` Junio C Hamano [this message]
2009-05-06 17:55 ` Finn Arne Gangstad
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=7vr5z2ungj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=julien@danjou.info \
/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).