Re: [boost] Git: maintaining super-project

In the git world, it's more common for develop to occur on "master" and for set releases to go to a "release" branch (with tags). On Wed, Dec 4, 2013 at 6:33 AM, Vladimir Prus wrote:

On 04.12.2013 15:27, Daniel James wrote:

...

On 4 December 2013 11:16, Vladimir Prus wrote:

...

We're back to square one.

You made a lot of assumptions and had a discussion where no one knew what they were talking about. So you have to go back to square one.

Checking out master branch of the superproject

...

will only get you master branches of everything if:

- as soon as anybody commits anything to master branch of his library, he creates a pull request for super project

- this pull request is merged quickly

Do you expect both conditions will hold?

Why do you think we're going to be using pull requests for the master repository?

Because no other mechanism has been documented anywhere that I can see, and because at this point, if some other mechanism is to be used, it would have been designed and documented already, prior to switching to git?

- Volodya

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