Re: [RFC 1/2] Use remote information in .git/config

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 22, 2005, 00:49 UTC
Message-ID: <Pine.LNX.4.63.0511220139120.6187@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vhda5lf4t.fsf@assigned-by-dhcp.cox.net>

Hi,

On Mon, 21 Nov 2005, Junio C Hamano wrote:

Show 9 quoted lines

> Once we start thinking about allowing the template mechansim to
> give default "config" information to newly created repositories,
> having everything in one file may make things a bit awkward to
> handle.  When you managed to make your colleage interested in
> git development, you can let her copy your remotes/junio.  Once
> you moved remotes/ to .git/config file, while you would not want
> her to use copy of your .git/config verbatim without updating at
> least user.name, you would want to have her use other pieces in
> the .git/config, including [remote.jnio] bits.

Well, obviously I would patch git-fetch/-pull/-push to have an option ("--store") to store the current parameters under a certain nick name in the config ;-)

Or add a little option (which is easy) to generate commands which can be piped into a little script (think "xmodmap -pke").

Show 6 quoted lines

> The following comments are not about your patch but I am having
> a feeling that we ended up having too much flexibility.  It may
> not necessarily be a bad thing when we view git as pure
> plumbing, but it makes things confusing to have too many "you
> could do it this way if you want to gain XXX, as long as you are
> careful about YYY".

I wouldn't be so sad about the flexibility. It is an open source project, and the strength therein lies in many people having many (yes, even stupid) ideas, and trying to get them in. In the long run, the dumb ideas are thrown out, but what remains is a collection of gems.

So, it might be confusing for a noobee, but that's what we have Documentation/tutorial for.

Show 10 quoted lines

> Most of the time, what we recommend are the BCP, but
> knowledgeable users can deviate from that, to gain some
> advantage (e.g. reduced disk space using an incomplete
> repository, convenience of having more than one checked-out
> trees at the same time, not having to migrate to all UTF-8
> system) over the BCP if they are willing to sacrifice something
> else or their use pattern is not affected negatively by what
> they are losing (e.g. can live without an access to ancient
> history, be very careful when pruning and fetching, do not have
> people whose names cannot be spelled in KOI-8).

'xactly. For example, I can do

	ln -s .gitgrafts .git/info/grafts

and have the effect that Linus just called "nasty". Point is, if I choose to do so, I can. Easily.

Ciao, Dscho