From 0c24b290ae02b2ab3304f51d5e11e85eb3659eae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= Date: Tue, 16 Feb 2010 18:19:18 +0000 Subject: 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. --- pod/perlrepository.pod | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'pod/perlrepository.pod') diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index af2229d750..2f29aef7de 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: -- cgit v1.2.1