From: Jeff King <peff@peff.net>
To: Peter Wu <peter@lekensteyn.nl>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC] [PATCH] remote: add new --fetch option for set-url
Date: Mon, 24 Nov 2014 17:54:57 -0500 [thread overview]
Message-ID: <20141124225457.GA9942@peff.net> (raw)
In-Reply-To: <1660121.8PEbpzfRYH@al>
On Mon, Nov 24, 2014 at 11:47:30PM +0100, Peter Wu wrote:
> > Right. My original complaint was only that "--fetch" is not as
> > orthogonal to "--push" (and an optionless set-url) as it could be. I
> > think the alternatives for going forward are basically:
> >
> > 1. Name it something besides --fetch (but that's rather clunky).
>
> It is not orthogonal to --push in the config, but the behavior exposed
> to the user is orthogonal unless I am missing something?
My complaint is that you have three possible options to provide: --push,
--fetch, or no option at all. And "--fetch" sometimes behaves like no
option, and sometimes not. Which is the confusing/non-orthogonal part.
> I can understand that --fetch sounds a bit weird, what about this
> natural translation:
>
> "git remote: set the URL (only the fetch one) for NAME to URL"
> git remote set-url --only=fetch NAME URL
>
> "git remote: set the URL (only the push one) for NAME to URL"
> git remote set-url --only=push NAME URL
> (obsoletes --push)
>
> "git remote: set the URL (both) for NAME to URL"
> git remote set-url --only=both NAME URL
> (it would be nice if --only=both (weird!) can be removed in the
> future such that the option is more natural)
>
> "git remote: set the URL for NAME to URL"
> git remote set-url NAME URL
> (current behavior: YOU git guru knows what I do right?)
Yeah, I think that addresses my concern (because it explicitly leaves
no-option as a historical curiosity, and not as an implicit version of
"--both").
> > 3. Live with it. Probably address the weirdness in the documentation.
> >
> > 4. Do nothing, drop the patch.
> >
> > I think I'd be OK with (3), with an appropriate documentation update.
>
> I prefer 1 for now as it avoids the extra manual action I have to take
> when changing URLs.
I'm not sure if I was clear on (3), but "live with it" was "live with
your original patch". Which I think you would also be happy with.
-Peff
next prev parent reply other threads:[~2014-11-24 22:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:18 [RFC] [PATCH] remote: add new --fetch option for set-url Peter Wu
2014-11-19 19:08 ` Jeff King
2014-11-19 19:42 ` Peter Wu
2014-11-19 20:17 ` Jeff King
2014-11-19 20:48 ` Peter Wu
2014-11-19 20:29 ` Junio C Hamano
2014-11-19 20:52 ` Peter Wu
2014-11-19 21:00 ` Junio C Hamano
2014-11-19 20:58 ` Junio C Hamano
2014-11-19 21:18 ` Junio C Hamano
2014-11-19 21:28 ` Peter Wu
2014-11-24 21:45 ` Peter Wu
2014-11-24 22:04 ` Junio C Hamano
2014-11-24 22:16 ` Peter Wu
2014-11-24 22:22 ` Jeff King
2014-11-24 22:47 ` Peter Wu
2014-11-24 22:54 ` Jeff King [this message]
2014-11-24 23:05 ` Junio C Hamano
2014-11-24 23:27 ` Peter Wu
2014-11-25 4:08 ` Jeff King
2014-11-25 4:55 ` Junio C Hamano
2014-11-25 5:01 ` Jeff King
[not found] ` <CAPc5daWh4hnKsTMpaW-TvCmVDfU+rzCezrAHcLgXDG6RVvzXHA@mail.gmail.com>
2014-11-25 11:43 ` Peter Wu
2014-11-25 11:36 ` Peter Wu
2014-11-29 13:31 ` Philip Oakley
2014-12-02 17:45 ` Peter Wu
2014-12-02 23:50 ` 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=20141124225457.GA9942@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peter@lekensteyn.nl \
/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).