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

[Peter Baumann <waste.manager@gmx.de>]

On Wed, Aug 08, 2007 at 02:52:14PM -0500, Sparks, Sam wrote:
>  
> 
> >-----Original Message-----
> >From: Peter Baumann [mailto:waste.manager@gmx.de] 
> >Sent: Wednesday, August 08, 2007 2:37 PM
> >To: Sparks, Sam
> >Cc: git@vger.kernel.org
> >Subject: Re: Git'ing a non-labeled set of sources
> >
> >On Wed, Aug 08, 2007 at 01:59:38PM -0500, Sparks, Sam wrote:
> >> Hello All,
> >> 
> >> Please excuse me if this is an ignorant question; I'm new to 
> >git and my
> >> have overlooked something in the documentation.
> >> 
> >> I'm attempting to obtain a snapshot of source code from an 
> >unlabeled git
> >> branch in a public repository. I've found in the documentation that a
> >> timestamp cannot be used to specify a particular version of 
> >source code,
> >> but I believe I can work with the commit value as returned by 'git
> >> show'.
> >> 
> >> However, I have been unsuccessful in my attempts to use this 
> >identifier
> >> to clone or checkout the associated source tree. Has anyone been
> >> successful in using git to successfully replicate an 
> >unlabeled version
> >> of sources in a repository?
> >> 
> >> Here is my latest attempt:
> >> /dir_i_want_to_replicate $ git show --pretty=short
> >> commit 5b1313fb2758ffce8b624457f777d8cc6709608d
> >> Author: ....
> >> 
> >> /replication_dir $ git clone git://www.denx.de/git/u-boot.git
> >> u-boot-mpc83xx
> >> Blah blah blah..
> >>  100% (4378/4378) done
> >> /replication_dir/u-boot-mpc83xx/ $ git checkout
> >> 5b1313fb2758ffce8b624457f777d8cc6709608d
> >> error: pathspec '5b1313fb2758ffce8b624457f777d8cc6709608d' 
> >did not match
> >> any. 
> >> 
> >
> >Because there is no 5b1313fb2758ffce8b624457f777d8cc6709608d in the
> >repo.
> >
> >  $ git clone git://www.denx.de/git/u-boot.git
> >  Initialized empty Git repository in /tmp/u-boot/.git/
> >  remote: Generating pack...
> >  remote: Done counting 40938 objects.
> >  remote: Deltifying 40938 objects.
> >  remote:  100% (40938/40938) done
> >  Indexing 40938 objects...
> >  remote: Total 40938 (delta 32545), reused 39302 (delta 31040)
> >  100% (40938/40938) done
> >  Resolving 32545 deltas...
> >  100% (32545/32545) done
> >
> >  $ cd u-boot; git-rev-list --all|grep ^5b1
> >  5b1d713721c3ea02549940133f09236783dda1f9
> >
> >-Peter
> 
> Hmmm. There must be something I am not understanding about git.
> When I run the same command on my existing git repository, I get the
> following:
> $ git-rev-list --all | grep ^5b1
> 5b1313fb2758ffce8b624457f777d8cc6709608d
> 5b1d713721c3ea02549940133f09236783dda1f9
> 
> Does git allow the removal of commits? I don't understand how I was able
> to download it a couple of months ago, but it is no longer accessible.
> 
> Thanks for the quick reply,
> Sam

If the branch was rebased, then yes. But this is not nice for
contributers, so it is normally the rule to not rebase a published
branch. But e.g. the branch 'pu' on git.git is a branch which will be
rebased. This is mentioned by Junio in his notes from the maintainer.

What made me wonder is, if you have the commit localy, why can't you
check it out? Please try a git-fsck --full run, to see if you have a
corrupt repo.

-Peter