[perl.git] branch blead, updated. v5.14.0-327-gd23ed4f

In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/d23ed4f3a45ba6d4fd1addb59dd6fca9360e2aff?hp=ddd2cc91d6090d4bcc45a8bb113437dd58fd2335>

- Log -----------------------------------------------------------------
commit d23ed4f3a45ba6d4fd1addb59dd6fca9360e2aff
Author: Jim Cromie (via RT) <perlbug-followup@perl.org>
Date:   Sat May 28 18:39:48 2011 -0700

    perlhack.pod: fix perlbug invocation
    
    In perlhack,
    
      % perlbug -s "[PATCH] $(git log -1 --format=%s HEAD)" -f 0001-*.patch
    
    is incomplete; --format=%s needs a proper value.
    Use --oneline instead, as it also --abbrev(iates) sha1
    
    $ git log --oneline -1
    c8dfc96 regexp.h: repair linux perf compilation
    
    Note that HEAD is optional, but just as clear as <branch-name>.
-----------------------------------------------------------------------

Summary of changes:
 pod/perlhack.pod |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 5e85f4b..f8f8bdd 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -60,7 +60,7 @@ Assuming your patch consists of a single git commit, you can send it to
 perlbug with this command line:
 
   % git format-patch -1
-  % perlbug -s "[PATCH] $(git log -1 --format=%s HEAD)" -f 0001-*.patch
+  % perlbug -s "[PATCH] $(git log -1 --oneline HEAD)" -f 0001-*.patch
 
 The perlbug program will ask you a few questions about your email
 address and the patch you're submitting. Once you've answered them you

--
Perl5 Master Repository

• [perl.git] branch blead, updated. v5.14.0-327-gd23ed4f by Dave Mitchell