From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3 v2] Make "git-remote rm" delete refs acccording to fetch specs
Date: Sun, 01 Jun 2008 01:28:05 -0700 [thread overview]
Message-ID: <7vve0tbluy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080601063051.GH12896@spearce.org> (Shawn O. Pearce's message of "Sun, 1 Jun 2008 02:30:51 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> I think the behavior in 2/2 and 3/3v2 is the best we can do,...
Oh, I think you already know I agree with that. I was just pointing out
that the extra niceness would not have mattered that much in practice, but
if the code is already written and is not crappy, why not ;-)
Not blindly assuming that the remote nickname matches the actualy used
namespace under refs/remotes _is_ a good bugfix regardless of the issue of
overlapping configuration.
next prev parent reply other threads:[~2008-06-01 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 3:59 [PATCH 3/3] Make "git-remote rm" delete refs acccording to fetch specs Shawn O. Pearce
2008-06-01 4:28 ` [PATCH 3/3 v2] " Shawn O. Pearce
2008-06-01 4:40 ` Shawn O. Pearce
2008-06-01 5:29 ` Junio C Hamano
2008-06-01 6:30 ` Shawn O. Pearce
2008-06-01 8:28 ` Junio C Hamano [this message]
2008-06-02 17:10 ` Jon Loeliger
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=7vve0tbluy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 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.