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

how to make "full" copy of a repo

From
Christoph Anton Mitterer <calestyo@scientia.net>
Date
Mar 28, 2015, 02:56 UTC
Message-ID
<1427511397.19633.52.camel@scientia.net>
Hey.

I was looking for an ideally simple way to make a "full" copy of a git repo. Many howtos are floating around on this on the web, with also lots of voodoo.

First, it shouldn't be just a clone, i.o.w.
- I want to have all refs (local/remote branches/tags) and of course all
objects from the source repo copied as is.
So it's local branches should become my local branches and not remote
branches as well - and so on.
Basically I want to be able to delete the source afterwards (and all
backups ;) ) and not having anything lost.
- It shouldn't set the source repo as origin or it's branches as remote
tracking branches, as said it should be identical the source repo, just
"freshly copied" via the "Git aware transport mechanisms".
- Whether GC or repacking happens, I don't care, as long as nothing that
is still reachable in the source repo wouldn't get lost (or get lost
once I run a GC in the copied repo).
- Whether anything that other tools have added to .git (e.g. git-svn
stuff) get's lost, I don't care.
- It should work for both, bare and non-bare repos, but it's okay when
it doesn't copy anything that is not committed or stashed.

I'd have said that either: $ git clone --mirror URl-to-source-repo copy for the direction from "outside" the source to a copy, or alternatively: $ cd source-repo $ git push --mirror URl-to-copy for the direction from "within" the source to a copy with copy being an empty bare or non-bare repo, would do the job.

But:
a) but the git-clone(1) part for --mirror:
   >and sets up a refspec configuration such that all these refs are
   >overwritten by a git remote update in the target repository.
   kinda confuses me since I wanted to get independent of the source
   repo and this ssems to set up a remote to it?
b) do I need --all --tags for the push as well?
c) When following
   https://help.github.com/articles/duplicating-a-repository/
   it doesn't seem as if --mirror is what I want because they seem to
   advertise it rather as having the copy tracking the source repo.
   Of course I read about just using git-clone --bare, but that seems to
   not copy everything that --mirror does (remote-tracking branches,
   notes).
   So I'm a bit confused...
1) Is it working like I assumed above?
2) Does that also copy things like git-config, hooks, etc.?
3) Does it copy the configured remotes from the source?
4) What else is not copied by that? I'd assume anything that is not
   tracked by git and the stash of the source?

Thanks a lot, Chris.

Next: Kevin D
Message 1 of 9 in “how to make "full" copy of a repo”
  1. Christoph Anton MittererMar 28, 2015
  2. Kevin DMar 28, 2015
  3. Christoph Anton MittererMar 29, 2015
  4. Kevin DMar 29, 2015
  5. Duy NguyenMar 30, 2015
  6. Junio C HamanoMar 30, 2015
  7. Torsten BögershausenMar 28, 2015
  8. Ævar Arnfjörð BjarmasonMar 28, 2015
  9. Christoph Anton MittererMar 29, 2015

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.