From: Junio C Hamano <gitster@pobox.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2018, #01; Sun, 9)
Date: Mon, 10 Dec 2018 19:26:45 +0900 [thread overview]
Message-ID: <xmqqtvjlisnu.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20181210035238.GA2104@archbookpro.localdomain> (Denton Liu's message of "Sun, 9 Dec 2018 22:52:38 -0500")
Denton Liu <liu.denton@gmail.com> writes:
> On Mon, Dec 10, 2018 at 12:21:05PM +0900, Junio C Hamano wrote:
>
>> And the "story" is not "If you have remote.$name.url and want to
>> move its value to remote.$name.pushurl while setting the former to a
>> new value, then..." I want to know why the user gets in such a
>> situation in the first place.
> ...
> The following is the story that led to me writing the feature in the
> first place:
> ...
OK, so in essense, it is quite similar to the following,
>> .... Perhaps you originally had a R/W URL that always
>> require authentication, but now you want to use an anonymous R/O URL
>> for your fetch traffic without having to authenticate? If there is
>> a model situation to make all of these four hold, perhaps it can be
>> added somewhere to help users who would find the new feature useful
>> discover it.
i.e.
You may have started your interaction with the repository
with a single authenticated URL that can be used for both
fetching and pushing, but over time you may have become sick
of having to authenticate only to fetch. In such a case,
you can feed an unauthenticated/anonymous fetch URL to
set-url with this option, so that the authenticated URL that
you have been using for pushing becomes the pushURL, and the
new, unauthenticated/anonymous URL will be used for
fetching.
With something like that in the documentation, I think the users
won't be puzzled by a feature that is seemingly a bit too niche, I
would think.
Thanks.
next prev parent reply other threads:[~2018-12-10 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 8:42 What's cooking in git.git (Dec 2018, #01; Sun, 9) Junio C Hamano
2018-12-09 9:03 ` Denton Liu
2018-12-10 3:21 ` Junio C Hamano
2018-12-10 3:52 ` Denton Liu
2018-12-10 10:26 ` Junio C Hamano [this message]
2018-12-09 20:31 ` pw/add-p-select, was " Johannes Schindelin
2018-12-10 10:42 ` Phillip Wood
2018-12-11 9:56 ` Johannes Schindelin
2018-12-11 14:48 ` Phillip Wood
2019-01-21 20:58 ` Johannes Schindelin
2019-01-22 20:27 ` Phillip Wood
2018-12-10 18:53 ` Josh Steadmon
2018-12-11 1:43 ` Junio C Hamano
2018-12-10 20:05 ` Elijah Newren
2018-12-10 21:50 ` Ævar Arnfjörð Bjarmason
2018-12-11 1:49 ` Junio C Hamano
2018-12-11 1:48 ` Junio C Hamano
2018-12-11 2:00 ` Stefan Beller
2018-12-11 6:17 ` Junio C Hamano
2018-12-16 21:48 ` Alban Gruin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtvjlisnu.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).