* [RFC] Subtle differences in passing configs to git clone
@ 2017-02-21 11:36 Lars Schneider
2017-02-21 17:47 ` Jeff King
0 siblings, 1 reply; 2+ messages in thread
From: Lars Schneider @ 2017-02-21 11:36 UTC (permalink / raw)
To: Git List; +Cc: Jeff King
Hi,
I stumbled across the following today:
(1) git -c foo.bar="foobar" clone <URL>
--> uses the config temporarily
(2) git clone -c foo.bar="foobar" <URL>
--> uses the config and writes it to .git/config
This was introduced in 84054f7 ("clone: accept config options on the
command line") and it makes total sense. However, I think this subtitle
difference can easily confuse users.
I think we should tell the users that we've written to .git/config.
Maybe something like this:
git clone -c foo.bar="foobar" <URL>
Cloning into 'test'...
Writing foo.bar="foobar" to local config...
remote: Counting objects: 2152, done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 2152 (delta 19), reused 0 (delta 0), pack-reused 2119
Receiving objects: 100% (2152/2152), 328.66 KiB | 217.00 KiB/s, done.
Resolving deltas: 100% (1289/1289), done.
What do you think?
Thanks,
Lars
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [RFC] Subtle differences in passing configs to git clone
2017-02-21 11:36 [RFC] Subtle differences in passing configs to git clone Lars Schneider
@ 2017-02-21 17:47 ` Jeff King
0 siblings, 0 replies; 2+ messages in thread
From: Jeff King @ 2017-02-21 17:47 UTC (permalink / raw)
To: Lars Schneider; +Cc: Git List
On Tue, Feb 21, 2017 at 12:36:25PM +0100, Lars Schneider wrote:
> I stumbled across the following today:
>
> (1) git -c foo.bar="foobar" clone <URL>
>
> --> uses the config temporarily
>
>
> (2) git clone -c foo.bar="foobar" <URL>
>
> --> uses the config and writes it to .git/config
>
> This was introduced in 84054f7 ("clone: accept config options on the
> command line") and it makes total sense.
Yep, they were designed to match.
> However, I think this subtitle difference can easily confuse users.
>
> I think we should tell the users that we've written to .git/config.
> Maybe something like this:
>
> git clone -c foo.bar="foobar" <URL>
> Cloning into 'test'...
> Writing foo.bar="foobar" to local config...
> remote: Counting objects: 2152, done.
> remote: Compressing objects: 100% (33/33), done.
> remote: Total 2152 (delta 19), reused 0 (delta 0), pack-reused 2119
> Receiving objects: 100% (2152/2152), 328.66 KiB | 217.00 KiB/s, done.
> Resolving deltas: 100% (1289/1289), done.
>
> What do you think?
<shrug> I don't find it confusing, but I can see how one might. Since
"clone" is already pretty chatty, I don't mind adding the extra message.
-Peff
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-02-21 17:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-21 11:36 [RFC] Subtle differences in passing configs to git clone Lars Schneider
2017-02-21 17:47 ` Jeff King
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.