Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: initializing remote clone but files already there
Date: Thu, 20 Jul 2006 23:32:45 +0200	[thread overview]
Message-ID: <20060720213245.GM13776@pasky.or.cz> (raw)
In-Reply-To: <f36b08ee0607201241t6160b1eqb4f0b255b02499a7@mail.gmail.com>

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

      reply	other threads:[~2006-07-20 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20 19:41 initializing remote clone but files already there Yakov Lerner
2006-07-20 21:32 ` Petr Baudis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060720213245.GM13776@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=iler.ml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox