On Wed, Aug 08, 2007 at 13:59:38 -0500, Sparks, Sam wrote:Clone and pull, over git protocol, only ask the server for objects referenc= ed by any refs -- plus all objects those depend on. Which does not necessarily mean all commits, because references may be removed. If a branch (ie. ref in refs/heads) is removed or rewound (moved to point to commit that is not descendant of what it pointed to before), some commits m= ay become dangling. Clone and pull won't know such commits exist and therefore won't be able to ask server to provide them. I bet that if you do 'git lost-found' here, it will find something and this commit will be among the finds, or predecessor of one of them. It seems that git pull only accepts refs as arguments. So you'll have to create a branch at that commit in the origin to get it over to destination. --=20 Jan 'Bulb' Hudec <bulb@ucw.cz>
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| David Woodhouse | [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more dr... |
| KAMEZAWA Hiroyuki | Re: 2.6.23-mm1 |
git: | |
| David Miller | Re: [PATCH 3/3] Convert the UDP hash lock to RCU |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Evgeniy Polyakov | Re: 2.6.25-rc8: FTP transfer errors |
