From: Andreas Schwab <schwab@linux-m68k.org>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: git@vger.kernel.org
Subject: Re: git fetch --reference
Date: Tue, 03 Sep 2013 19:19:46 +0200 [thread overview]
Message-ID: <m2ppspkekt.fsf@linux-m68k.org> (raw)
In-Reply-To: <ae657fa74373b58feba41615d335504e@meuh.org> (Yann Droneaud's message of "Tue, 03 Sep 2013 18:55:29 +0200")
Yann Droneaud <ydroneaud@opteya.com> writes:
> So what's the best way to do a git fetch <remote>, copying objects from
> another local repository
> to resolve delta ?
IMHO the best way is to add a remote for the local repository, fetch
from it, then fetch from <remote>.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2013-09-03 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 16:55 git fetch --reference Yann Droneaud
2013-09-03 17:19 ` Andreas Schwab [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=m2ppspkekt.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=ydroneaud@opteya.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.