From: David Woodhouse <dwmw2@infradead.org>
To: git@vger.kernel.org
Subject: Clone with local alternates?
Date: Wed, 19 Apr 2006 00:48:51 +0100 [thread overview]
Message-ID: <1145404132.16166.97.camel@shinybook.infradead.org> (raw)
Often I want to clone a remote repository but would like to use an
existing local source tree as 'alternates'.
One way of doing this is to clone the local tree with 'git-clone -l -s',
find the latest common commit shared with the remote tree to be fetched,
revert to that with 'git-reset --head $last' and then pulling from the
remote.
Is that _really_ the best way of doing it though? It would be better if
we just had a '--local-alternates=/foo' option to git-clone when cloning
a remote repository.
--
dwmw2
next reply other threads:[~2006-04-18 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 23:48 David Woodhouse [this message]
2006-04-18 23:56 ` Clone with local alternates? Shawn Pearce
2006-04-18 23:59 ` David Woodhouse
2006-04-19 0:19 ` [PATCH] Document git-clone --reference Shawn Pearce
2006-04-19 8:39 ` Clone with local alternates? David Woodhouse
2006-04-19 9:42 ` Eric W. Biederman
2006-04-19 9:36 ` Eric W. Biederman
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=1145404132.16166.97.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).