From: Ævar Arnfjörð Bjarmason Date: Tue, 16 Feb 2010 18:19:18 +0000 (+0000) Subject: Mention why it's a good idea to use topic branches for everything X-Git-Tag: accepted/trunk/20130322.191538~9478^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0c24b290ae02b2ab3304f51d5e11e85eb3659eae;p=platform%2Fupstream%2Fperl.git Mention why it's a good idea to use topic branches for everything Most of this is derived from Dan Golden's E-Mail to me on perl5-porters with the subject "[PATCH] Add comments to gv.c about variable implementation" where I'd submitted a patch without using a topic branch. --- diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index af2229d..2f29aef 100644 --- a/pod/perlrepository.pod +++ b/pod/perlrepository.pod @@ -299,6 +299,14 @@ which is the short form of % git branch orange % git checkout orange +Creating a topic branch makes it easier for the maintainers to rebase +or merge back into the master blead for a more linear history. If you +don't work on a topic branch the maintainer has to manually cherry +pick your changes onto blead before they can be applied. + +That'll get you scolded on perl5-porters, so don't do that. Be +Awesome. + Then make your changes. For example, if Leon Brocard changes his name to Orange Brocard, we should change his name in the AUTHORS file: