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

Re: Git Confusion

From
Jeff King <peff@peff.net>
Date
May 29, 2009, 13:52 UTC
Message-ID
<20090529135242.GA30926@coredump.intra.peff.net>
In-Reply-To
<m3d49sauru.fsf@localhost.localdomain>
On Fri, May 29, 2009 at 06:44:26AM -0700, Jakub Narebski wrote:
Show 7 quoted lines
> > Usually such a repo is bare, and gets updates only by push. In that
> > case, enabling the update hook to run update-server-info is sufficient.
> > But in your case, you are actually working on the remote repo via commit
> > and other means, so there is no convenient way to always
> > update-server-info after a change.
> 
> Well, he can always add git-update-server-info to post-commit hook.

That covers committing, but what about reset, rebase, "branch -f", etc? I don't think there is a catch-all for all the ways that a repo can be updated locally.

> > Is there a particular reason you cloned over http instead of over ssh?
> Or git protocol?

Yes, that would work fine, too. I mentioned ssh because he already indicated that he was able to ssh into the box (and may or may not have the git daemon set up).

-Peff
Previous: Jakub NarebskiNext: Paul Tarjan
Message 4 of 10 in “Git Confusion”
  1. Paul TarjanMay 29, 2009
  2. Jeff KingMay 29, 2009
  3. Jakub NarebskiMay 29, 2009
  4. Jeff KingMay 29, 2009
  5. Paul TarjanMay 29, 2009
  6. Avery PennarunMay 29, 2009
  7. Jeff KingMay 29, 2009
  8. Sitaram ChamartyMay 30, 2009
  9. Jakub NarebskiMay 29, 2009
  10. Sitaram ChamartyMay 30, 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.