Stefan Näwe <[email protected]> writes:
>> Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
>> or a tag (from refs/tags/) ?
Because they are common enough, and doing the same for an arbitrary
object is just as easy to do something like:
git clone -n
git checkout $an_arbitrary_commit_object_name^0
>> Background: At $dayjob we're using some kind of 'hidden' refs (in
>> refs/releases/)
>> to communicate between the 'branch integrator' (who creates the ref in
>> refs/releases/)
>> and the 'build master' who wants to build that ref.
While I wasn't paying much attention to this, I vaguely recall that
people pointed out that using a fresh clone every time may not be
what you want to do in the first place, and I happen to agree with
them (and that is why I am not very much interested in this topic).
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
