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

Re: [PATCH 2/2] repo-config: learn the flag "--no-local"

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 8, 2006, 21:10 UTC
Message-ID
<Pine.LNX.4.63.0606082308010.28722@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<BAYC1-PASMTP040660E676E00AD1631524AE8B0@CEZ.ICE>
Hi,
On Thu, 8 Jun 2006, Sean wrote:
Show 7 quoted lines
> 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?

If I have --user vs. --repo, then I expect the setting to be active for the user vs. the repository, respectively.

Show 14 quoted lines
> > 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; 
Clearly, you have not met the same administrators as I did.
> obviously we can't guess all the creative ways git will be used beforehand.

That is right, but is it for somebody else to decide the creative way, or for you?

Ciao, Dscho

Previous: SeanNext: Sean
Message 15 of 21 in “repo-config: learn the flag "--no-local"”
  1. 2/2 repo-config: learn the flag "--no-local"Johannes Schindelin, Jun 8, 2006
  2. Lukas SandströmJun 8, 2006
  3. Johannes SchindelinJun 8, 2006
  4. Karl HasselströmJun 8, 2006
  5. Aneesh Kumar K.VJun 8, 2006
  6. Jakub NarebskiJun 8, 2006
  7. Johannes SchindelinJun 8, 2006
  8. Alex RiesenJun 8, 2006
  9. Junio C HamanoJun 8, 2006
  10. SeanJun 8, 2006
  11. Johannes SchindelinJun 8, 2006
  12. SeanJun 8, 2006
  13. Johannes SchindelinJun 8, 2006
  14. SeanJun 8, 2006
  15. Johannes SchindelinJun 8, 2006
  16. SeanJun 8, 2006
  17. Jakub NarebskiJun 8, 2006
  18. Johannes SchindelinJun 8, 2006
  19. Jakub NarebskiJun 8, 2006
  20. Aneesh Kumar K.VJun 8, 2006
  21. Johannes SchindelinJun 8, 2006

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.