Re: [boost] [git] annotated SVN synchronization for boost.test (example only)

-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter A. Bigot Sent: Tuesday, January 14, 2014 5:24 PM To: boost@lists.boost.org Subject: Re: [boost] [git] annotated SVN synchronization for boost.test (example only)

On 01/14/2014 11:00 AM, Beman Dawes wrote:

...

On Mon, Jan 13, 2014 at 12:36 PM, Peter A. Bigot wrote:

...

On 01/13/2014 06:28 AM, Gennadiy Rozental wrote:

...

Peter A. Bigot writes:

Below is an annotated sequence of (bash) command-line git operations

...

that I used in a local copy of Boost.Test to understand what was happening in it, with no intention of proposing this be what the maintainers actually do with the module.

Thank you. I need to get my hands dirty and finally switch to git locally. At some point I'll need this (I hope ;))

In the interests of reducing pain: I recommend against using those steps.

The problem, of course, is that your procedure is overwhelmingly complex for a new git user. That's why the docs we've been working on try to stick to very basic git.

True. The problem with the docs is that they don't explain what the commands are doing and why (or why not) use them.

Rote application works until something goes wrong, then people get confused about what happened.

Definitely - this is a serious flaw with very, very many sets of instructions. * They don't say why the next step is being taken. * They don't say how one can tell it has worked OK. * Or how to check that it has worked OK. * And what to do if it hasn't. For example, even the bootstrap process description fails this test. (I'm still unclear what b2 headers does! - and I'm not certain I fully understand what bootstrap does either). I know this makes the instructions longer but IMO it's well worth it. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com