From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] repo-config: learn the flag "--no-local"
Date: Thu, 08 Jun 2006 22:55:29 +0200 [thread overview]
Message-ID: <e6a2rt$n6p$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0606082235020.28405@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> BTW it is the same reason I would rather not see /etc/gitconfig: it
> meddles with an existing configuration. If you want to give defaults, you
> can use a skeleton for $HOME, and templates for $GIT_DIR. As a user, I
> would be very surprised if the behaviour of git changed from one day to
> the other without my changing anything.
I agree wholeheartily. I guess that the 'skeleton' part has yet to be
written...
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-08 20:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 11:31 [PATCH 2/2] repo-config: learn the flag "--no-local" Johannes Schindelin
2006-06-08 11:37 ` Lukas Sandström
2006-06-08 11:41 ` Johannes Schindelin
2006-06-08 13:37 ` Karl Hasselström
2006-06-08 15:35 ` Aneesh Kumar K.V
2006-06-08 18:36 ` Jakub Narebski
2006-06-08 20:17 ` Johannes Schindelin
2006-06-08 14:06 ` Alex Riesen
2006-06-08 16:25 ` Junio C Hamano
[not found] ` <20060608123652.6c3acf76.seanlkml@sympatico.ca>
2006-06-08 16:36 ` Sean
2006-06-08 20:24 ` Johannes Schindelin
[not found] ` <20060608163045.abd03553.seanlkml@sympatico.ca>
2006-06-08 20:30 ` Sean
2006-06-08 20:42 ` Johannes Schindelin
[not found] ` <20060608165525.e42917d2.seanlkml@sympatico.ca>
2006-06-08 20:55 ` Sean
2006-06-08 21:10 ` Johannes Schindelin
[not found] ` <20060608172315.15c2af3c.seanlkml@sympatico.ca>
2006-06-08 21:23 ` Sean
2006-06-08 20:55 ` Jakub Narebski [this message]
2006-06-08 21:03 ` Johannes Schindelin
2006-06-08 21:15 ` Jakub Narebski
2006-06-08 15:32 ` Aneesh Kumar K.V
2006-06-08 20:18 ` Johannes Schindelin
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='e6a2rt$n6p$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).