Subject: Re: [boost] [git help] Documenting common modular boost workflows
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2013-10-19 12:56:25
> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Beman Dawes
> Sent: Saturday, October 19, 2013 4:03 PM
> To: Boost Developers List
> Subject: [boost] [git help] Documenting common modular boost workflows
> I think we need to document simple suggested modular boost workflows. Each workflow could start
> with the assumption that the steps described in https://svn.boost.org/trac/boost/wiki/TryModBoost
> have been completed.
> Workflows might include:
> 1) Switch to the "develop" branch, fix a minor problem, test, commit, switch back to
> 2) Same as (1) but also push to remote.
> 3) Same as (2) but also merge develop to master.
> 4) Same as (3) but end by submitting a pull request to the boost super-project.
> I don't mind writing the actual wiki pages, but am a little hobbled by being a TortoiseGit rather
> command line git user, and by never having worked with sub-modules.
Most users will be a little hobbled by only being TortoiseGits ;-)
So I think TortoiseGit examples should be the priority (with command lines later).
--- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk