From: Felipe Contreras <felipe.contreras-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: David Aguilar <davvid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
"Bráulio Bhavamitra"
<brauliobo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] build: add default configuration
Date: Wed, 18 Sep 2013 22:49:06 -0500 [thread overview]
Message-ID: <CAMP44s3Q6ummNmLovw0BuGR=yNWfmRFmrg9xb50OawMwKznfBw@mail.gmail.com> (raw)
In-Reply-To: <ab38a1b5-e354-4e32-8ede-46a401ef8053.maildroid@localhost>
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.
> and asking users to manually fix up thousands of machines is a bad idea.
Users don't package /etc/gitconfig outside git.
>>> 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.
--
Felipe Contreras
--
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.
next prev parent reply other threads:[~2013-09-19 3:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 13:14 [PATCH] build: add default configuration Felipe Contreras
[not found] ` <1379423650-1311-1-git-send-email-felipe.contreras-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-18 18:13 ` David Aguilar
2013-09-18 18:23 ` Felipe Contreras
[not found] ` <CAMP44s35_emnh9Kce433oy1JW66xB2vaN5f5OO7VF1XqoO=YGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-19 2:30 ` David Aguilar
2013-09-19 3:49 ` Felipe Contreras [this message]
[not found] ` <CAMP44s3Q6ummNmLovw0BuGR=yNWfmRFmrg9xb50OawMwKznfBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-20 18:31 ` David Aguilar
[not found] ` <4d9893bc-c812-457b-9f40-ebe01d37df53-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-09-20 21:02 ` Felipe Contreras
[not found] ` <523cb7e7a2d70_5010801e84148e8-9w9IBNBfMV1mR6Xm/wNWPw@public.gmane.org>
2013-09-21 0:44 ` David Aguilar
[not found] ` <573b085d-d7fd-453e-8f2b-f83ba1f85ef7-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-09-21 3:54 ` Felipe Contreras
[not found] ` <CAMP44s14hn5qvG_88e_7FDx9ExSSu8DsVFUa5uhU-aOzSFy4MQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-21 6:33 ` David Aguilar
[not found] ` <749d06d0-3e17-49bf-8299-86c99c0dd9f5-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-09-21 11:07 ` Felipe Contreras
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='CAMP44s3Q6ummNmLovw0BuGR=yNWfmRFmrg9xb50OawMwKznfBw@mail.gmail.com' \
--to=felipe.contreras-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=brauliobo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=davvid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).