summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorJim Cromie (via RT) <perlbug-followup@perl.org>2011-05-28 18:39:48 -0700
committerDavid Mitchell <davem@iabyn.com>2011-05-31 15:33:19 +0100
commitd23ed4f3a45ba6d4fd1addb59dd6fca9360e2aff (patch)
tree8ead44151581b0bfa0d934b6890f4184adf89f82 /pod/perlhack.pod
parentddd2cc91d6090d4bcc45a8bb113437dd58fd2335 (diff)
downloadperl-d23ed4f3a45ba6d4fd1addb59dd6fca9360e2aff.tar.gz
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>.
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 5e85f4ba74..f8f8bdd82c 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