git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: junkio@cox.net, lukass@etek.chalmers.se, git@vger.kernel.org
Subject: Re: [PATCH 2/2] repo-config: learn the flag "--no-local"
Date: Thu, 8 Jun 2006 16:55:25 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP040660E676E00AD1631524AE8B0@CEZ.ICE> (raw)
Message-ID: <20060608165525.e42917d2.seanlkml@sympatico.ca> (raw)
In-Reply-To: <Pine.LNX.4.63.0606082235020.28405@wbgn013.biozentrum.uni-wuerzburg.de>

On Thu, 8 Jun 2006 22:42:17 +0200 (CEST)
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> I'd like to know how --home tells you when this key is retreived.

I honestly don't know.  How does --user tell you when this key is retrieved?

> The admin has no business messing around with the users' configuration. 
> And if she absolutely wants to be a BOFH, she can fire up any editor, or 
> copy .gitconfig to /root/.gitconfig, use git-config, and copy it back, or 
> do what she does all the time: "su <user>". But frankly, we should not 
> support a bad work flow.
> 
> 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.

This seems like a rather heavy handed policy for an application to enforce.
To my mind, these types of decisions are best left up to administrators; 
obviously we can't guess all the creative ways git will be used beforehand.

Sean

  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 [this message]
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
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=BAYC1-PASMTP040660E676E00AD1631524AE8B0@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=lukass@etek.chalmers.se \
    /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).