On Wed, 10 Sep 2008, Ramagudi Naziir wrote:
Hi David,
On Sun, Sep 7, 2008 at 9:27 AM, <david@xxxxxxx> wrote:
On Sun, 7 Sep 2008, Ramagudi Naziir wrote:
Hi all,
I have several local git repositories on my machine. I'm the only
user, and use them only locally. Now, sometimes when I need to work
remotely, I just rsync my repositories to my laptop, and keep working
there. When I finish (few hours, days or sometimes weeks later), I
just rsync everything back to my local git repositories on my main
workstation, and continue working there.
Now I was wondering whether it's OK or whether there are bad
implication I might not think of working this way. For example, maybe
some of these little git files are named differently on each machine,
and rsyncing them back and forth makes me piling a lot of clutter (in
that case maybe git-gc will clean up everything). Or maybe something
else horrid is going on and I really should just use git-push or pull.
the git files are names by their content so you don't need to worry about
them being named differently
But can I end up having a lot of clutter ? e.g. if these files change,
then rsync will copy the new files, and the old ones will still be
kept, piling up like crud. is this correct ? is it problematic ? will
git-gc fix it ?
git keeps copies of all the old files around anyway (that's it's purpose
after all ;-)
when git gc runs it creates pack files to replace the individual files,
but unless you run git gc --prune it does not remove anything and the
individual files hang around.
so when you do the rsync back and forth you should have it delete files
from the target that aren't on the source (or run git gc --prune
afterwords)
David Lang
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
