[Clfs-dev] CLFS 2.0.0 Release Announcement
William Harrington
berzerkula at cox.net
Sat Apr 20 17:21:39 PDT 2013
On Apr 20, 2013, at 6:38 PM, Jean-Philippe MENGUAL wrote:
> Ok thanks, but what does it mean? Did I fetch the 2.0.0 book? Are
> trunk and 2.0.0
> branch similar? Do I need some additional twick to have 2.0.0?
> Nothing mentions
> the checkout succeeds despite this message.
Howdy,
There is no 2.0.0 branch. When checking out, the branch is master at
the current head, and 2.0.0 tag is a link at the current commit so it
is all the same. You can check out to other tags and set head to when
those tags were made and then if you want to create your own branch
checkout -b <branch>. If you don't do the checkout command, you are
working in master, which is as of now, the same point as 2.0.0 till
the next commit.
I haven't done a clfs release other than 2.0.0-RC1. I created a tag at
2.0.0 and development moves on.
git clone git://git.cross-lfs.org/cross-lfs.git clfs-1.2.0
Initialized empty Git repository in /srv/userhome/kb0iic/
clfs-1.2.0/.git/
remote: Counting objects: 47461, done.
remote: Compressing objects: 100% (13710/13710), done.
remote: Total 47461 (delta 35641), reused 44559 (delta 33062)
Receiving objects: 100% (47461/47461), 25.86 MiB | 15.44 MiB/s, done.
Resolving deltas: 100% (35641/35641), done.
kb0iic at meander:~$ cd clfs-1.2.0/
kb0iic at meander:~/clfs-1.2.0$ git branch
* master
kb0iic at meander:~/clfs-1.2.0$ git checkout clfs-1.2.0
Note: moving to 'clfs-1.2.0' which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
git checkout -b <new_branch_name>
HEAD is now at 8ba9f15... Updated testlog and errata URLs for CLFS 1.2.0
kb0iic at meander:~/clfs-1.2.0$ git checkout clfs-2.0.0
Previous HEAD position was 8ba9f15... Updated testlog and errata URLs
for CLFS 1.2.0
HEAD is now at b9579bd... Add --enable-arch to util-linux multilib
configure commands.
kb0iic at meander:~/clfs-1.2.0$ git branch
* (no branch)
master
Now that should give you a better idea. When head and checkout will be
at the same commit, then the results should be what you received.
Not sure if I got it all correct, I'm still learning git everyday.
Sincerely,
William Harrington
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-dev-clfs.org/attachments/20130420/8df0944a/attachment-0001.htm>
More information about the Clfs-dev
mailing list