In perl.git, the branch blead has been updated
<https://perl5.git.perl.org/perl.git/commitdiff/9b91093d3e74d13a6e4f67269a587f4ab397998a?hp=2ae26641a3d7283c7b9df71fd2a4bb202a1bcb36>
- Log -----------------------------------------------------------------
commit 9b91093d3e74d13a6e4f67269a587f4ab397998a
Author: Zefram <zef...@fysh.org>
Date: Mon Dec 11 21:25:38 2017 +0000
document rules for identifying smoke-me branches
-----------------------------------------------------------------------
Summary of changes:
pod/perlgit.pod | 3 +++
1 file changed, 3 insertions(+)
diff --git a/pod/perlgit.pod b/pod/perlgit.pod
index d8d75c1cb0..000d6ac0d4 100644
--- a/pod/perlgit.pod
+++ b/pod/perlgit.pod
@@ -852,6 +852,9 @@ on other OSes test the change before you commit it to blead.
Fortunately, there is a way to get your change smoke-tested on various
OSes: push it to a "smoke-me" branch and wait for certain automated
smoke-testers to report the results from their OSes.
+A "smoke-me" branch is identified by the branch name: specifically, as
+seen on perl5.git.perl.org it must be a local branch whose first name
+component is precisely C<smoke-me>.
The procedure for doing this is roughly as follows (using the example of
of tonyc's smoke-me branch called win32stat):
--
Perl5 Master Repository
