[git-users] Merging repositories and their histories

2008-08-18 Thread Peter Waller

I have three repositories, A, B and C. I wish to bring them together
to only one repository (.), where they are in a directory called ./
Archive, so.. ./Archive/{A,B,C}. Then I plan at a later date to move
files arbitrarily from ./Archive/{A/B/C}/Something and into ./
Something{A/B/C}. (A lame example, but illustrates what I want to do).

I would like ./SomethingA (etc) to have their complete histories from
the old repository. I thought I would do this with the subtree
mechanism described at 
http://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html,
but I have had little luck getting it to work as I desired.

Firstly, I create a new repository with git init, then I "remote add
A", "merge" and "readtree". This immediately leads to two copies of
A's files, in ./Archive/A/Files and ./Files. The files in Archive/A do
not have any history.

Then if I do this with B, the files do not appear in ./, but again
they do not have their history. I have tried using git log --follow -
M, but this does not seem to help. I have tried numerous other
strategies, but none seem to work.

I thought I would get around my problems doing the merge, then moving
the files - this works for A, but when I move on to B, the files are
not in ./, so I can't move them. If I read-tree some files, git status/
commit shows them as 'new files' and does not seem to recognize them
as old files with a long history.

Any help would be appreciated on this problem.

Thanks in advance,

- Peter
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en
-~--~~~~--~~--~--~---



[git-users] keeping database dump in git (sql or sql.gz)

2008-08-18 Thread Sujee Maniyam

Hi guys
I am keeping a database dump in git.
uncompressed db.sql- size : 41M
compressed  db.sql.gz  - size : 4M

I am trying to figure out which format to use.   Gzippd version is
smaller, but  I am not sure if git can save only the deltas thus
keeping the repository lean.  Text format is big, but the deltas are
easier to figure out and ongoing deltas can keep the repository small.

Any thoughts on this?

thanks a lot
/SM
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en
-~--~~~~--~~--~--~---