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

Re: Incremental Backup of repositories using Git

From
Jeff King <peff@peff.net>
Date
May 8, 2025, 20:20 UTC
Message-ID
<20250508202033.GE18229@coredump.intra.peff.net>
In-Reply-To
<029701dbc054$a6e9af00$f4bd0d00$@nexbridge.com>
On Thu, May 08, 2025 at 04:06:08PM -0400, rsbecker@nexbridge.com wrote:
> As a possible alternative, would some kind of information presented via the proposed
> git blame-tree series (or call it git annotate-tree perhaps) be useful for this enhancement?
> I am not sure what the results will look like, but it might be useful and then cached by
> the backup strategy. I'm grasping at straws, though.

I don't think so. From an efficiency perspective, your best git-aware backup really is going to be packfiles representing slices of history, depending on each other. I.e., bundles or something approximating them.

-Peff
Previous: rsbecker@nexbridge.comNext: Michal Suchánek
Message 11 of 14 in “Incremental Backup of repositories using Git”
  1. Akash SMay 5, 2025
  2. Justin ToblerMay 5, 2025
  3. Abhishek DalmiaMay 6, 2025
  4. Justin ToblerMay 6, 2025
  5. Abhishek DalmiaMay 8, 2025
  6. Jeff KingMay 8, 2025
  7. Abhishek DalmiaMay 27, 2025
  8. Michal SuchánekMay 8, 2025
  9. Jeff KingMay 8, 2025
  10. rsbecker@nexbridge.comMay 8, 2025
  11. Jeff KingMay 8, 2025
  12. Michal SuchánekMay 9, 2025
  13. Michal SuchánekMay 9, 2025
  14. Michal SuchánekMay 9, 2025

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.