Hi

I agree with you that I can see all the tags now. E.g
> git tag -l
> 1.3.0
<..> 
> 1.4.3
> 1.4.5
> 1.4.6
works perfectly. But last week it didn't work.
Also today 
> git checkout 1.4.6
> Previous HEAD position was cfa6df1... Release 1.4.3
> HEAD is now at 1df36b5... Release 1.4.6
works like a charm, which it didn't last week. No idea what triggered the 
change. Consulted my /var/log/apt/history.log and didn't see any updates of 
git.

Also today I was able to call in my buildr4osgi checkout "braid update buildr 
1.4.6" , which fail last week and triggered my questions about not seeing the 
tags in my buildr checkout.

Sorry for the noise and thanks for your feedback.

Best regards

Niklaus

> Hi,
> 
> I had a look and as far as I can tell there are tags for 1.4.5 and
> 1.4.6, none for 1.4.4 but a branch instead. If you look at github you
> can see them at
> 
> https://github.com/apache/buildr/tree/1.4.4
> https://github.com/apache/buildr/tree/1.4.5
> https://github.com/apache/buildr/tree/1.4.6
> 
> I will create a tag for 1.4.4 based on the same location as the branch
> so we can have a tag for 1.4.4 as well.
> 
> What was the command you were using to switch to the tag?
> 
> On Fri, Apr 27, 2012 at 5:54 PM, Niklaus Giger
> 
> <niklaus.gi...@member.fsf.org> wrote:
> > Hi
> > 
> > I recently wanted to switch to the 1.4.6 of buildr in my local git
> > checkout, but was unable to do so. Only tags up to 1.4.3 are present.
> > 
> > Would it be difficult to add these tags?
> > 
> > Thanks in advance.
> > 
> > Best regards
> > 
> > --
> > Niklaus Giger

Reply via email to