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

Re: Fetch from remote A, push to remote B

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
May 31, 2007, 07:28 UTC
Message-ID
<46a038f90705310028y6f180214s9018f8af5e71d0ed@mail.gmail.com>
In-Reply-To
<46a038f90705302253s68b70311h3feac7404fa23933@mail.gmail.com>
On 5/31/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> Is there an easy way to get a "passthrough" repo setup so I can say on a cronjob
>
>   git-fetch remoteA
>   git-push ssh+git://host/path/to/repoB.git remotes/remoteA/<all>
After mucking about with stuff like...

find .git/refs/remotes/origin -type f -printf '%P\0' | xargs -0 -IHEADNAME git-push git+ssh://git.catalyst.net.nz/var/git/moodle-r2-testing.git origin/HEADNAME:HEADNAME

I figured out that a bare repo did the trick
  # set things up
  git-clone --bare git+ssh://host-a/bla.git bla-transfer.git
  # on cron do
  GIT_DIR=bla-transfer.git git-fetch git+ssh://host-a/bla.git
  GIT_DIR=bla-transfer.git git-push --all git+ssh://host-b/bla.git
cheers!
martin
Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 5 in “Fetch from remote A, push to remote B”
  1. Martin LanghoffMay 31, 2007
  2. Martin LanghoffMay 31, 2007
  3. Martin LanghoffJun 1, 2007
  4. Martin LanghoffJun 1, 2007
  5. Martin LanghoffJun 1, 2007

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.