Re: GIT 0.99.7d, and end of week status.

From: Alan Chandler <alan@chandlerfamily.org.uk>
Date: Sep 25, 2005, 20:43 UTC
Message-ID: <200509252143.23905.alan@chandlerfamily.org.uk>
In-Reply-To: <7vaci1nfwa.fsf@assigned-by-dhcp.cox.net>

On Sunday 25 Sep 2005 19:47, Junio C Hamano wrote: ...

Show 6 quoted lines

>
> One straightforward way which would work for everybody would be
> (provided you do not have git-src in the current directory):
>
>    $ git clone http://kernel.org/pub/scm/git/git.git git-src
>    $ cd git-src

I did the above just after your announcement but before the tags etc had got there (see my earlier question in this thread).

>    $ git reset --hard v0.99.7d

Didn't do this ...

> Then you can say:
>
>     $ git fetch origin tag v0.99.7d

 Did this
...

Show 10 quoted lines

> Now, how would you check out the v0.99.7d tag?  There are two
> ways to think about it.
>
> If the reason you want v0.99.7d, not "master" nor "pu", is you
> would want to stay with the 0.99.7 but get all the latest safer
> fixes, then you can just checkout "maint" branch instead, like
> this:
>
>     $ git checkout -f maint
>

I am rather new to all this, but this last step puzzles me.

Before this step, and using gitk --all, I can see the maintenance branch, but its currently connected to the point where the v0.99.7c tag is and not where your latest tag is.

So if I followed these instructions, now, wouldn't I just get the v0.997c tag?

Does that mean I have missed some step along the way to get the maint branch position moved to the new tag?

-- 
Alan Chandler
http://www.chandlerfamily.org.uk