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

Re: How to ignore changes on remote

From
Jakub Narebski <jnareb@gmail.com>
Date
Mar 23, 2010, 17:47 UTC
Message-ID
<hoaus7$3br$1@dough.gmane.org>
In-Reply-To
<201003231820.51618.johan@herland.net>
Johan Herland wrote:
Show 7 quoted lines
> I'm rolling out Git at my $DAYJOB to a few hundred developers, and I 
> instruct them to
> 
>         git config --global push.default tracking
> 
> immediately after installing Git. Which sucks, but is the only sane 
> thing I can do to prevent this problem from haunting us.
Why not have administrator use
         git config --system push.default tracking
once (and/or setup skeleton for /etc/gitconfig)?
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Johan HerlandNext: Johan Herland
Message 12 of 14 in “How to ignore changes on remote”
  1. Howard MillerMar 23, 2010
  2. Sylvain RabotMar 23, 2010
  3. Howard MillerMar 23, 2010
  4. Alexander IljinMar 23, 2010
  5. Santi BéjarMar 23, 2010
  6. Howard MillerMar 23, 2010
  7. Sylvain RabotMar 23, 2010
  8. Scott ChaconMar 23, 2010
  9. Howard MillerMar 23, 2010
  10. Johannes SixtMar 23, 2010
  11. Johan HerlandMar 23, 2010
  12. Jakub NarebskiMar 23, 2010
  13. Johan HerlandMar 23, 2010
  14. Junio C HamanoMar 23, 2010

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.