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

A system administration use case for git

From
Jon Seymour <jon.seymour@gmail.com>
Date
Apr 22, 2009, 08:33 UTC
Message-ID
<2cfc40320904220133l5ab567f3q46608793b93f0e1f@mail.gmail.com>
Hello all, it's been quite a while.

And, no, I don't care that you ripped out git-rev-list --merge-order, it was fun while it lasted and it was still a cool (if under appreciated) algorithm :-)

I've got a system administration use case that I know git does 99.9% of. I am wondering if the last 0.1%.

It'd be nice to do this on arbitrary (non-git-controlled) file system tree:
* calculate the git hashes of the tree (without making copies of the
files in the tree)
* archive the tree hashes
* rsync the tree hashes to another place
* work out which files aren't available in the other place's git repo
* rsync those files the the other place

Is there a way to easily achieve this with git's existing tool set or a higher layer?

jon.
Next: Martin Langhoff
Message 1 of 8 in “A system administration use case for git”
  1. Jon SeymourApr 22, 2009
  2. Martin LanghoffApr 22, 2009
  3. Uwe Kleine-KönigApr 23, 2009
  4. Johannes SixtApr 23, 2009
  5. Uwe Kleine-KönigApr 23, 2009
  6. Jon SeymourApr 22, 2009
  7. Martin LanghoffApr 22, 2009
  8. Jon SeymourApr 22, 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.