Re: Dose git-fetch need --reference option like git-clone?
- From
Mike Hommey <mh@glandium.org>
- Date
- Nov 11, 2007, 08:38 UTC
- Message-ID
- <20071111083840.GA17231@glandium.org>
- In-Reply-To
- <46dff0320711110009y713c7d38q7b1457c92daecef6@mail.gmail.com>
On Sun, Nov 11, 2007 at 04:09:55PM +0800, Yin Ping wrote:
Show 13 quoted lines
> I want to track remote repsotory (say remoteA) on my local repository > (say localB), so i do the following in directory localB > $ git remote add remoteA git://remoteAUrl > $ git fetch remoteA > This will fetch all objects from git://remoteAUrl if localB and > remoteA don't have common objects. > > If I already have a cloned remoteA on local machine (say > /path/to/remoteACloned), I want to do following to reduce the net > traffic as git-clone: > git fetch --reference /path/to/remoteACloned remotedA > > Is this reasonable? Or is there already a resolution for this case?
It would probably be reasonable to have this on git-remote. Anyways, you can easily do it yourself by editing .git/objects/info/alternates and adding /path/to/remoteACloned in it. You can happily git fetch after that.
Mike