Doing this would require I got tracked which one comes from which. So
it would imply some logic (and db) over it. With the hardlinking way,
it wouldn't require anything. The idea is that you don't have to do
anything else in the server.
I understand that it would be imposible to do it for windows users
(but using cygwin), but for *nix ones yes...
2012/11/15 Andrew Ardill <andrew.ard...@gmail.com>:
> On 15 November 2012 11:40, Javier Domingo <javier...@gmail.com> wrote:
>> Hi Andrew,
>> The problem about that, is that if I want to delete the first repo, I
>> will loose objects... Or does that repack also hard-link the objects
>> in other repos? I don't want to accidentally loose data, so it would
>> be nice that althought avoided to repack things, it would also
>> hardlink them.
> Hi Javier, check out the section below the one I linked earlier:
>> How to stop sharing objects between repositories?
>> To copy the shared objects into the local repository, repack without the -l
>> git repack -a
>> Then remove the pointer to the alternate object store
>> rm .git/objects/info/alternates
>> (If the repository is edited between the two steps, it could become corrupted
>> when the alternates file is removed. If you're unsure, you can use git fsck
>> check for corruption. If things go wrong, you can always recover by replacing
>> the alternates file and starting over).
> Andrew Ardill
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html