Re: git faq

On Wednesday, January 22, 2025 at 1:20:08 PM UTC-5 doc...-Skx+k2Pw7SNmR6Xm/[email protected] 
wrote:

On Wed, Jan 22, 2025 at 08:42:25AM -0800, Jon Ericson wrote: 
> It might also help to look at the git checkout manpage 
> <https://git-scm.com/docs/git-checkout> for details of how to get the 
> branch you are looking for. 
> 
> In addition, all releases are tagged and listed on GitHub 
> <https://github.com/openssl/openssl/releases>. If you are just interested 
> in released code, you can grab a tarball from there or checkout by tag 
> <https://stackoverflow.com/questions/35979642/what-is-
git-tag-how-to-create-tags-how-to-checkout-git-remote-tags> 
> . 
> 
> On Wed, Jan 22, 2025 at 8:32???AM Tomas Mraz <[email protected]> wrote: 
> 
> > The stable branches are simply named openssl-x.y starting from openssl- 
> > 3.0. 
> > 
> > The development branch for the next major or minor release is still the 
> > master branch. 
> > 
> > The public git repository is at https://github.com/openssl/openssl/ or 
> > https://github.com/openssl/openssl.git for direct git access. 
> > 
> > Tomas Mraz, OpenSSL 
> > 
> > On Wed, 2025-01-22 at 08:58 -0700, 'The Doctor' via openssl-users 
> > wrote: 
> > > Is theire a git faq to obtain the branch of openssl you would like 
> > > to 
> > > try out from 3.0 upwards? 
> > > 

Please stop topposting we are Openssl not Micrsoft. 

So what I am trying to do is 

if I can do a 

git pull 


command 

then this seems to be more efficient. 


-- 
Member - Liberal International This is [email protected] Ici [email protected] 
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist 
rising! 
Look at Psalms 14 and 53 on Atheism ; 
Birthdate - 29 January 1969 Redhill, Surrey, England, Uk


git pull doesn't sound like the command you want.

All our development is merged to the master branch, and for each release, 
at the time we ship its alpha version, we create a branch named 
openssl-<major>-<minor> (as tomas noted above)

After that, for that release, any stabilization changes are committed to 
that branch.  Alpha, Beta and final releases have tags applied to them in 
the git tree, in the pattern 
openssl-<major>-<minor>-<patch>-[alpha<N>|beta<N>]

Each of those tags and branches can be inspected using the git checkout 
command

for example, if you want to see what the tree looks like at the openssl 
3.2.0 beta1 release, you can run:
git checkout openssl-3.2.0-beta1

or if you want to see what the final 3.4.0 release looks like:
git checkout openssl-3.4.0

If you want to see where we are in the development of an unreleased version 
of openssl 3.3, you can check out its branch:
git checkout openssl-3.3
which will contain any unreleased commits since the last tag for that 
release

Or if you want to just see the head of the development tree (currently 
tracking 3.5 development) you can just run
git checkout master

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/6b12f56e-1057-48be-93a7-37181007783dn%40openssl.org.