At file:///home/vila/src/bzr/cleanup/better-branch-names/ ------------------------------------------------------------ revno: 5018 revision-id: [email protected] parent: [email protected] committer: Vincent Ladeuil <[email protected]> branch nick: better-branch-names timestamp: Wed 2010-02-10 09:00:58 +0100 message: Review comment: let's bikeshed !!
=== modified file 'doc/developers/HACKING.txt' --- a/doc/developers/HACKING.txt 2010-02-09 08:39:38 +0000 +++ b/doc/developers/HACKING.txt 2010-02-10 08:00:58 +0000 @@ -131,7 +131,9 @@ Using a meaningful name for your branch will help you and the reviewer(s) better track the submission. Use a very succint description of your submission and prefix it with bug number if needed (lp:~mbp/bzr/484558-merge-directory -for example). +for example). Alternatively, you can suffix with the bug number +(lp:~jameinel/bzr/export-file-511987). + Why make a local copy of bzr.dev? ---------------------------------
-- bazaar-commits mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/bazaar-commits
