projects / p5sagit/p5-mst-13.2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9d77ce3)
Mention why it's a good idea to use topic branches for everything
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>
Tue, 16 Feb 2010 18:19:18 +0000 (18:19 +0000)
committerÆvar Arnfjörð Bjarmason <avarab@gmail.com>
Tue, 16 Feb 2010 18:19:18 +0000 (18:19 +0000)
commit0c24b290ae02b2ab3304f51d5e11e85eb3659eae
tree26400d56d593dc49e015b5f55c3d923c4daefdb2tree | snapshot
parent9d77ce3f21b279b465beef4cb5fcbc9efafef340commit | diff
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 diff | blob | blame | history
Unnamed repository; edit this file to name it for gitweb.