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

Re: Managing websites with git

From
Jason Riedy <jason@acm.org>
Date
Dec 2, 2008, 00:46 UTC
Message-ID
<87k5ajflp0.fsf@sparse.dyndns.org>
In-Reply-To
<20081130172717.GA7047@coredump.intra.peff.net>
And David Bryson writes:
> One really should not push to a non-bare repo.
WHAT?!?!?!
And Jeff King responds:
> It's in master and should be in 1.6.1, but it is a config option that
> defaults to "warn" for now, so as not to break existing setups.
WHAT?!?!?!

I do this all the time. I clone from my main working directory onto some cluster / MPP where the build system is all wonky. Once I get everything building, I push back to a branch (often new) in my main working directory. Then I can merge the build changes whenever I get a chance.

Pushing from these systems often is much, much easier than pulling from the origin. Sometimes you're working in temporary space on a back-end node; you can connect out but you cannot connect in.

I've gotten a few people interested in git for managing these nearly one-off build problems. git is the first system that has "just worked" for them. Their having to configure each repo eliminates the "just works" factor.

It feels like newer gits make more and more decisions about what I shouldn't do.

Jason
Previous: Jeff KingNext: Jeff King
Message 4 of 10 in “Managing websites with git”
  1. Felix AndersenNov 30, 2008
  2. David BrysonNov 30, 2008
  3. Jeff KingNov 30, 2008
  4. Jason RiedyDec 2, 2008
  5. Jeff KingDec 2, 2008
  6. Jason RiedyDec 2, 2008
  7. Jeff KingDec 2, 2008
  8. Junio C HamanoDec 2, 2008
  9. Leo RazoumovDec 2, 2008
  10. Todd A. JacobsJan 3, 2009

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.