Bug 650923

Summary: Unquoted string "c" may clash with future reserved word
Product: [Fedora] Fedora Reporter: Michal Fojtik <mfojtik>
Component: perlAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: cweyl, iarnell, kasal, lkundrak, mmaslano, ppisar, psabata, rc040203, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 15:40:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
git send-email patch none

Description Michal Fojtik 2010-11-08 11:53:36 UTC 
Description of problem:

When using git send-email I got this error:

/tmp/p/0004-Added-support-for-F5-load_balancer-collection-in-GoG.patch
Unquoted string "c" may clash with future reserved word at /usr/lib/perl5/_h2ph_pre.ph line 162.
Illegal character in prototype for main::__INT16_C : c at /usr/lib/perl5/_h2ph_pre.ph line 162.
OK. Log says:

Also last patch is not processes by git send-email and not sent.

Version-Release number of selected component (if applicable):

mfojtik ~ $ perl --version
This is perl 5, version 12, subversion 2 (v5.12.2) built for i386-linux-thread-multi


How reproducible:

Complicated :-) But I uploaded that patch as an attachment. So you can try to create a empty git repo and then call git send-email --thread /tmp/p [<- put that patch file here] --subject 'blabla'
Comment 1 Petr Šabata 2010-11-08 12:28:30 UTC 
Michal,

please, upload the mentioned patch. Thank you :)

-- Petr
Comment 2 Michal Fojtik 2010-11-08 14:37:34 UTC 
Created attachment 458753 [details]
git send-email patch
Comment 3 Petr Šabata 2010-11-08 15:40:58 UTC 

*** This bug has been marked as a duplicate of bug 643447 ***