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

Re: Way to "impersonate" remote or sync remotes without fetching everything?

From
KFKlaus Frank <vger.kernel.org@frank.fyi>
Date
Apr 14, 2025, 00:34 UTC
Message-ID
<351a6036-3bac-43f4-88b0-cd52240312cd@frank.fyi>
In-Reply-To
<CALnO6CALCFLWSs9HBWX13V_BUZkoeZuVjHVnF4_e0OMy3LfEjw@mail.gmail.com>
On 2025-04-13 23:52:14, D. Ben Knoble wrote:
> That all makes sense, except: why need the sync (cron) job? Treat a
> local copy as authoritative for you and push to all your remotes. This
> puts you in control at the cost of not happening automatically. (You
> could conceivably have a local cron job that did this.)

Cause I don't want to have it locally on e.g. a notebook that can break mainly :D (I know myself I won't be making enough backups if that is their primary location)

But I have been thinking about something similar earlier today. Maybe I should just trash my software forge (gitlab) and just use git from the cli via ssh. Then writing a cron job to do the syncing would also be easier as I'd have a local copy to work with and maybe add some Stagit sparkles to replace the web-ui (aka some static page generator for git repos) https://codemadness.org/stagit.html

(Still not quite satisfies with Stagit nor cgit, maybe I'll find something that needs, less files generated on the server side and some "git in javascript" to display the more exotic views instead of doing it server side like cgit does)

-- Klaus Frank

Previous: D. Ben KnobleNext: D. Ben Knoble
Message 5 of 6 in “Way to "impersonate" remote or sync remotes without fetching everything?”
  1. Klaus FrankApr 5, 2025
  2. D. Ben KnobleApr 11, 2025
  3. Klaus FrankApr 11, 2025
  4. D. Ben KnobleApr 13, 2025
  5. Klaus FrankApr 14, 2025
  6. D. Ben KnobleApr 14, 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.