"Shawn O. Pearce" <spearce@spearce.org> writes:It is not. The "git remote add" thing adds this to my .git/config: [remote "origin"] url = /tmp/git1 fetch = +refs/heads/*:refs/remotes/origin/* While clone normally does a bit more: [remote "origin"] url = /tmp/git1/.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master So, it's really $ git remote add origin url $ $EDITOR .git/config # or perhaps I missed the way to set the two # options easily. I find it so conveinient to have it for non-empty clones, it's frustrating to have to do it by hand for empty clones. -- Matthieu - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Arjan van de Ven | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interfaceforon access scanning |
| Patrick McHardy | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Eric W. Biederman | Re: namespace support requires network modules to say "GPL" |
git: | |
