Bazaar

Merge lp:~bialix/bzr/docs into lp:bzr

  1. docs
  2. Merge into bzr.dev
Proposed by Alexander Belchenko
Status: Merged
Approved by: John A Meinel
Approved revision: no longer in the source branch.
Merged at revision: 5366
Proposed branch: lp:~bialix/bzr/docs
Merge into: lp:bzr
Diff against target: 11 lines (+1/-0)
1 file modified
doc/developers/overview.txt (+1/-0)
To merge this branch: bzr merge lp:~bialix/bzr/docs
Reviewer Review Type Date Requested Status
John A Meinel Approve
Review via email: mp+31622@code.launchpad.net

Commit message

Fixed small formatting issue.

Description of the change

Fixed small formatting issue (after converting to html sublist was not converted to <ul>)

To post a comment you must log in.
Revision history for this message
John A Meinel (jameinel) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> Alexander Belchenko has proposed merging lp:~bialix/bzr/docs into lp:bzr.
>
> Requested reviews:
> bzr-core (bzr-core)
>
>
> Fixed small formatting issue (after converting to html sublist was not converted to <ul>)
>

 merge: approve

You could even put this into 2.2 if you based it on the 2.2 branch. This
is also the sort of trivial patch that you could land without waiting
for review if you wanted.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxYKwkACgkQJdeBCYSNAAPFiwCbB0p1JsItmyiOeHyIuynsYW/a
6y8Amwe6yPzAWpqs1u6dgj9KXBC9XdJs
=lFcB
-----END PGP SIGNATURE-----

review: Approve
Revision history for this message
Alexander Belchenko (bialix) wrote :

John A Meinel пишет:
> Review: Approve
> Alexander Belchenko wrote:
>> Alexander Belchenko has proposed merging lp:~bialix/bzr/docs into lp:bzr.
>>
>> Requested reviews:
>> bzr-core (bzr-core)
>>
>>
>> Fixed small formatting issue (after converting to html sublist was not converted to <ul>)
>>
>
> merge: approve
>
> You could even put this into 2.2 if you based it on the 2.2 branch. This
> is also the sort of trivial patch that you could land without waiting
> for review if you wanted.

I'm still can't figure out how to land my branches with all new pqm stuff.

--
All the dude wanted was his rug back

Revision history for this message
Andrew Bennetts (spiv) wrote :

sent to pqm by email

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/developers/overview.txt'
2--- doc/developers/overview.txt 2010-06-21 03:55:08 +0000
3+++ doc/developers/overview.txt 2010-08-03 09:39:46 +0000
4@@ -147,6 +147,7 @@
5 revision data that can be pointed to by various branches:
6
7 * Maintains storage of various history data at a URL:
8+
9 * Revisions (Must have a matching inventory)
10 * Digital Signatures
11 * Inventories for each Revision. (Must have all the file texts available).