Re: Git'ing a non-labeled set of sources

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jan Hudec
Date: Thursday, August 9, 2007 - 1:02 pm

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>
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Git'ing a non-labeled set of sources, Sparks, Sam, (Wed Aug 8, 11:59 am)
Re: Git'ing a non-labeled set of sources, Peter Baumann, (Wed Aug 8, 12:37 pm)
RE: Git'ing a non-labeled set of sources, Sparks, Sam, (Wed Aug 8, 12:52 pm)
Re: Git'ing a non-labeled set of sources, Peter Baumann, (Wed Aug 8, 1:17 pm)
RE: Git'ing a non-labeled set of sources, Sparks, Sam, (Wed Aug 8, 1:45 pm)
RE: Git'ing a non-labeled set of sources, Sparks, Sam, (Wed Aug 8, 1:59 pm)
Re: Git'ing a non-labeled set of sources, Alex Riesen, (Wed Aug 8, 2:20 pm)
Re: Git'ing a non-labeled set of sources, Jan Hudec, (Thu Aug 9, 1:02 pm)