user guide help (definitions of terms)
nmb at wartburg.edu
Sat Aug 8 16:14:55 BST 2009
On 2009-08-07 21:47 , Ian Clatworthy wrote:
> Neil Martinsen-Burrell wrote:
>> On 2009-08-07 09:34 , Inky 788 wrote:
>>> What's the proper
>>> procedure for cloning, making local changes, and asking to have those
>>> changes considered for inclusion?
>> The way to do
>> this is to make changes to the files in the doc/ subdirectory of the bzr
>> source-code. You can then push those changes as a Bazaar branch to
>> Launchpad where they will be reviewed for inclusion. I think it goes
>> like this:
>> $ bzr branch http://bazaar-vcs.org/bzr/bzr.dev
>> $ cd bzr.dev/doc/en/user-guide
>> $<hack, hack, hack>
>> $ bzr ci -m 'Improved documentation'
>> $ bzr push lp:~your_lp_username/bzr/20-doc-fixes
>> Then go to https://launchpad.net/your_lp_username/bzr/20-doc-fixes and
>> select "Propose for merging into another branch" to hand your changes
>> off to the developers for merging.
> Thanks - that's a good explanation.
> Did you mind updating http://bazaar-vcs.org/BzrGivingBack to reflect
> this (relatively new) process? I've had some offlist feedback in recent
> days highlighting that the current material there is neither correct nor
> sufficient for users wanting to contribute.
Done. It is much easier to understand with merge proposals. If
Launchpad merge proposals are in fact the recommended way to contribute
to Bazaar, do we need to change HACKING.txt? I'm willing to make the
changes there too, but I don't know that there is consensus on the topic.
More information about the bazaar