[GitHelp] Getting boost stable release from GitHub after git clone

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHelp] Getting boost stable release from GitHub after git clone

Boost - Dev mailing list
Hi, guys.

I would appreciate little help in understanding what is the right way
of switching to the latest stable boost release after git repository
is cloned.

My intention is to clone boost, because then, with new releases, I can
easily update it with git and switch (checkout) to the next "current"
release.

PS: I like that boost uses git =).
---
Kostia
Kyiv, Ukraine

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [GitHelp] Getting boost stable release from GitHub after git clone

Boost - Dev mailing list
On 29/10/2017 00:43, Kostiantyn Ponomarenko wrote:
> I would appreciate little help in understanding what is the right way
> of switching to the latest stable boost release after git repository
> is cloned.
>
> My intention is to clone boost, because then, with new releases, I can
> easily update it with git and switch (checkout) to the next "current"
> release.

In theory, just this should be sufficient:

   git checkout boost-1.65.1
   git submodule update --init --recursive


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [GitHelp] Getting boost stable release from GitHub after git clone

Boost - Dev mailing list
Thank you for the help.
---
Kostia
Kyiv, Ukraine


On Mon, Oct 30, 2017 at 12:58 AM, Gavin Lambert via Boost
<[hidden email]> wrote:

> On 29/10/2017 00:43, Kostiantyn Ponomarenko wrote:
>>
>> I would appreciate little help in understanding what is the right way
>> of switching to the latest stable boost release after git repository
>> is cloned.
>>
>> My intention is to clone boost, because then, with new releases, I can
>> easily update it with git and switch (checkout) to the next "current"
>> release.
>
>
> In theory, just this should be sufficient:
>
>   git checkout boost-1.65.1
>   git submodule update --init --recursive
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost