initializing remote clone but files already there

initializing remote clone but files already there

[Yakov Lerner]

There are two machines with slow ssh access. The
both have copy of same filetree that was synchronized
previously vi rsync. How do I put both trees under git control
as if they were clone on one other *but* (1) without creating
branches and (2) without copying files over (files are already
there) ?

Thanks
Yakov

Re: initializing remote clone but files already there

[Petr Baudis]

Dear diary, on Thu, Jul 20, 2006 at 09:41:48PM CEST, I got a letter
where Yakov Lerner <iler.ml@gmail.com> said that...
> There are two machines with slow ssh access. The
> both have copy of same filetree that was synchronized
> previously vi rsync. How do I put both trees under git control
> as if they were clone on one other *but* (1) without creating
> branches and (2) without copying files over (files are already
> there) ?

Put one tree under the git control and examine the initial commit in
detail (cg-log -v or git show --pretty=fuller or whatever). Now you want
to perform the initial commit in the other tree with exactly the same
metadata; log message should be easy, to carry over all the times and
stuff, you need to set GIT_AUTHOR_{NAME,EMAIL,DATE} and
GIT_COMMITTER_<dtto> based on the other initial commit details. That
should result in a same commit id. Then you need to just set up remote
branch origin just like you would set up any other remote branch.

Good luck,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam