From: Stefan Näwe <stefan.naewe@atlas-elektronik.com>
Date: Mon, 01 Jul 2013 07:04:46 GMT
Subject: Re: git clone -b
Message-ID: <51D12A0E.60709@atlas-elektronik.com>
In-Reply-To: <51CD7AB7.3040409@atlas-elektronik.com>

Am 28.06.2013 13:59, schrieb Stefan Näwe:
> Hi there!
> 
> Is there any reason why 'git clone -b' only takes a branch (from refs/heads/)
> or a tag (from refs/tags/) ?
> 
> 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. 
> 
> It would be a little easier if the build master could simply say
> 
>   git clone -b refs/releases/the-release-for-today URL
> 
> instead of: git clone... ; cd ... ; git fetch... ; git checkout....
> 
> Any answer or even a better idea to solve that is appreciated.
> 
> Stefan
> 

Anyone?

Thanks,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: Some people like learning Eskimo, but I can't get Inuit.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"