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

Re: gc/repack has no option to lose grafted parents

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Mar 6, 2014, 23:36 UTC
Message-ID
<CACPiFCLgoGP59sW73YFCt8Wq4hpxZUb0PBF-DzHz0JdxrYo4rw@mail.gmail.com>
In-Reply-To
<xmqqwqg6vrht.fsf@gitster.dls.corp.google.com>
On Thu, Mar 6, 2014 at 6:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
> Given that we in general frown upon long-term use of grafts (or
> "replace" for that matter), I am not sure if we want to go in that
> direction.
>
> Just a knee-jerk reaction, though.
Fair enough.

If I state my actual goals -- discarding old, uninteresting history, in a "rolling" fashion? (periodically using a script that says "forget anything older than one month") -- is there a better way?

The repository is not standalone, it receives pushes from hundreds of clients, and gets pulled from a couple of clients. All clients are "in sync", in that will be pulling every hour (vs a "time window" of one month).

At this stage, and with careful management (ie: custom gc scripts) git makes for an excellent async log/report transfer tool. We specially appreciate that it has "deep buffer".

cheers,
m
-- 
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff
Previous: Junio C HamanoNext: Duy Nguyen
Message 3 of 4 in “gc/repack has no option to lose grafted parents”
  1. Martin LanghoffMar 6, 2014
  2. Junio C HamanoMar 6, 2014
  3. Martin LanghoffMar 6, 2014
  4. Duy NguyenMar 7, 2014

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.