Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Regarding commits, refs, branches and "<em>et cetera</em>", Magnus answer just works (git remote update).</p> <p>But unfortunately there is no way to clone / mirror / update <strong>the hooks</strong>, as I wanted... </p> <p>I have found this very interesting thread about cloning/mirroring the hooks:</p> <p><a href="http://kerneltrap.org/mailarchive/git/2007/8/28/256180/thread" rel="nofollow noreferrer">http://kerneltrap.org/mailarchive/git/2007/8/28/256180/thread</a></p> <p>I learned:</p> <ul> <li><p>The "hooks" are not considered part of the repository contents.</p></li> <li><p>There is more data, like the ".git/description" folder, which does not get cloned, just as the hooks.</p></li> <li><p>The default hooks that appear in the "hooks" dir comes from the TEMPLATE_DIR</p></li> <li><p>There is this interesting "template" feature on git.</p></li> </ul> <p>So, I may either ignore this "clone the hooks thing", or go for a <code>rsync</code> strategy, given the purposes of my mirror (backup + source for other clones, only).</p> <p>Well... I will just forget about hooks cloning, and stick to the "git remote update" way.</p> <ul> <li>Sehe has just pointed out that not only "hooks" aren't managed by the clone / update process, but also stashes, rerere, etc... So, for a strict backup, rsync or equivalent would really be the way to go. As this is not really necessary in my case (I can afford not having hooks, stashes, and so on), like I said, I will stick to the "remote update".</li> </ul> <p>Thanks! Improved a bit of my own "git-fu"... :-)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload