git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] build: add default configuration

From
DADavid Aguilar <davvid-re5jqeeqqe8avxtiumwx3w@public.gmane.org>
Date
Sep 20, 2013, 18:31 UTC
Message-ID
<4d9893bc-c812-457b-9f40-ebe01d37df53@email.android.com>
In-Reply-To
<CAMP44s3Q6ummNmLovw0BuGR=yNWfmRFmrg9xb50OawMwKznfBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Felipe Contreras <felipe.contreras-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Show 19 quoted lines
>On Wed, Sep 18, 2013 at 9:30 PM, David Aguilar <davvid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>wrote:
>>>On Wed, Sep 18, 2013 at 1:13 PM, David Aguilar <davvid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>wrote:
>>>>
>>>> Will this not conflict with folks that supply their own gitconfig?
>>
>>> You mean people that provide their own ETC_GITCONFIG? If you mean
>> distributions, their packaging would override /etc/gitconfig, if you
>> mean people that have already a /etc/gitconfig, packaging systems
>> usually save the old one so they can solve the conflict manually
>(e.g.
>> /etc/gitconfig.pacsave). So no, it would not conflict.
>>
>> Yuck. Yes, that one. I package my own /etc/gitconfig (as we have long
>advertised as the "way to do it")
>
>You package /etc/gitconfig *outside* the git package? I don't see how
>that could have been ever advertised as the way to do it.
Okay so how exactly are we supposed to do it?  Duh, rpm is the right choice for redhat systems. 
>Users don't package /etc/gitconfig outside git.
Wrong. Existence proof: me. 
Show 15 quoted lines
>>>> I like the idea. Docs?  Also, should this not be done in the C side
>so that we don't waste time reading the config, and also prevent users
>from overriding these?
>>
>>> But we want them to be easily readable, and possibly allow
>> distributions to easily modify them.
>>
>> In that case I take it back -- I dont like that approach.  We want
>consistency, not divergence. This encourages the former.
>
>So you think we have more consistency right now? We don't even have a
>predefined /etc/gitconfig, that creates more inconsistency, as
>everybody's configs and aliases are very very different.
>
>This patch would definitely make things more consistent.
We don't need this patch to allow distros to modify aliases. Likewise, allowing the aliases to diverge is less consistent. Do it at a lower level. 
I also agree with Junio's notes about "ci". Something short that can add and remove from the index would be nice. 
-- 
David

-- 
You received this message because you are subscribed to the Google Groups "Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Previous: Felipe ContrerasNext: Felipe Contreras
Message 6 of 11 in “build: add default configuration”
  1. build: add default configurationFelipe Contreras, Sep 17, 2013
  2. David AguilarSep 18, 2013
  3. Felipe ContrerasSep 18, 2013
  4. David AguilarSep 19, 2013
  5. Felipe ContrerasSep 19, 2013
  6. David AguilarSep 20, 2013
  7. Felipe ContrerasSep 20, 2013
  8. David AguilarSep 21, 2013
  9. Felipe ContrerasSep 21, 2013
  10. David AguilarSep 21, 2013
  11. Felipe ContrerasSep 21, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.