| |
| |
Hi. I am setting up a local clone to track fltk releases.
git branch -r
origin/HEAD -> origin/master
origin/branch-1.0
origin/branch-1.1
origin/branch-1.3
origin/darkmode
origin/master
So, I used
Did this work? It should likely read 'git clone --branch branch-1.3
...'
The correct branch name would be 'branch-1.3'
Can I confirm that branch-1.3 is also 1.3.6 ? I am only
interested in the release branch.
No, a branch is a "moving target". Whenever a commit gets pushed the
branch gets updated (which you'd notice by running 'git fetch', 'git
pull', or similar). The 1.3 branch (branch-1.3) got at least one
commit after the release of 1.3.6 and will soon be release 1.3.7
(I'm working on it).
If you're interested in releases you should checkout the release
tags, see `git tag' which will show you all release tags, like this
(all 1.3 releases since 1.3.3):
$ git tag | grep '1\.3\.[3-9].*'
release-1.3.3
release-1.3.4
release-1.3.4-1
release-1.3.4-2
release-1.3.5
release-1.3.5rc1
release-1.3.5rc2
release-1.3.6
release-1.3.6rc1
release-1.3.6rc2
We're always adding a 'release-x.y.z' tag when a release is
finished.
Note also that the published release tarballs are not exactly
the same as you can pull from git. One notable exception is that the
tarballs contain a pre-built 'configure' script whereas git does
not.
Likewise origin/master is the 1.4 branch right ?
Yes, but as said above, the branch is moving (and there's no 1.4
release yet).
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/e526ac4a-015b-a8e5-b3f1-688f4d36d482%40online.de.
[ Direct Link to Message ] | |
|
| |
