# initializing remote clone but files already there 2 messages from 2006-07-20 to 2006-07-20. Participants: Yakov Lerner, Petr Baudis. Thread: https://gitlist.dev/t/4932 ## Yakov Lerner, 2006-07-20 19:41 Subject: initializing remote clone but files already there Message-ID: URL: https://gitlist.dev/e/f36b08ee0607201241t6160b1eqb4f0b255b02499a7%40mail.gmail.com ``` 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 ``` ## Petr Baudis, 2006-07-20 21:32 Subject: Re: initializing remote clone but files already there Message-ID: <20060720213245.GM13776@pasky.or.cz> URL: https://gitlist.dev/e/20060720213245.GM13776%40pasky.or.cz In-Reply-To: ``` Dear diary, on Thu, Jul 20, 2006 at 09:41:48PM CEST, I got a letter where Yakov Lerner 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_ 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 ```