Re: Patch queue management systems

[Steinar Bang <sb@dod.no>]

>>>>> Ted Zlatanov <tzz@lifelogs.com>:

SB> If that repository resides on the same server and is created with
SB> hardlinks to the real repo, it should also be cheap disk-usage-wise,
SB> at least initially....)

> Eh.

 cd /wherever/the/emacs/repo/lives
 git clone --mirror ./emacs.git ./emacs-feature-branches.git

If the git used is reasonably new, then all of the known-by-hash objects
in the new repository will be hardlinks to the original repo (which is
safe since these will never change).

So the new repository will initially use very little space on disk (all
history from the time of cloning will use the same inodes as the
original repository).

But as times goes and the emacs-feature-branches repo is filled by
clutter, the space usage of the feature branches repository will
increase.

Of course an easy way of doing housecleaning here, would be:
 cd /wherever/the/emacs/repo/lives
 rm -rf emacs-feature-branches.git
 git clone --mirror ./emacs.git ./emacs-feature-branches.git
and then let people repush their feature branches.