Re: [PATCH] Invoke git-repo-config directly.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Invoke git-repo-config directly.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:21

Junio C Hamano [off-list ref] writes:

(replying to myself ...)
Linus Torvalds [off-list ref] writes:
quoted
I agree that it is inconsistent as-is. So a patch to make it use the 
"git-repo-config" form (the argument being that internally, we use the 
full names) might be good if just for consistency.
If we do the dash-form for consistency's sake,...
Probably I should add that personally my preference is to standardize on
the dashless form.

Re: [PATCH] Invoke git-repo-config directly.

From: Qingning Huo <hidden>
Date: 2016-06-15 22:42:21

On Wed, Mar 15, 2006 at 01:35:22PM -0800, Junio C Hamano wrote:
Junio C Hamano [off-list ref] writes:
quoted
Linus Torvalds [off-list ref] writes:
quoted
I agree that it is inconsistent as-is. So a patch to make it use the 
"git-repo-config" form (the argument being that internally, we use the 
full names) might be good if just for consistency.
If we do the dash-form for consistency's sake,...
Probably I should add that personally my preference is to standardize on
the dashless form.
That would remove the possibility to run "git-push" in my scenario.  And
what is the benefit?  Wasting CPU cycles to an extra execve?
Duplicating git --exec-path to PATH?

Personally I recommend to always run git helper programs with absolute
path, this would remove all confusions, not play with users' PATH
environment, and save CPU cycles.

Qingning
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help