From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: "Björn Esser" <b.esser@pengutronix.de>, rhi@pengutronix.de
Subject: Re: [ptxdist] [PATCH] perl: Add patch for compatibility with recent libcrypt implementations.
Date: Thu, 10 Oct 2019 15:25:05 +0200 [thread overview]
Message-ID: <20191010132504.hydcq7yitubjqag3@falbala.home.lespocky.de> (raw)
In-Reply-To: <43574d3c6b642138588e856917960399e9cff40e.camel@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2439 bytes --]
Hei hei,
this is slightly offtopic, but let me answer anyways …
On Thu, Oct 10, 2019 at 02:45:03PM +0200, Björn Esser wrote:
> On Do, 2019-10-10 at 14:39 +0200, Roland Hieber wrote:
> > On Thu, Oct 10, 2019 at 10:44:45AM +0200, Björn Esser wrote:
> > > Signed-off-by: Björn Esser <b.esser@pengutronix.de>
> > > ---
> > > .../0001-It-s-lpthread-not-lpthreads.patch | 7 +++-
> > > ...-fix-build-failure-with-recent-glibc.patch | 39
> > > +++++++++++++++++++
> > > patches/perl-5.18.2/series | 3 +-
> > > 3 files changed, 47 insertions(+), 2 deletions(-)
> > > create mode 100644 patches/perl-5.18.2/0002-fix-build-failure-
> > > with-recent-glibc.patch
> > >
> > > diff --git a/patches/perl-5.18.2/0001-It-s-lpthread-not-
> > > lpthreads.patch b/patches/perl-5.18.2/0001-It-s-lpthread-not-
> > > lpthreads.patch
> > > index 319cefb2e..7a7bb1beb 100644
> > > --- a/patches/perl-5.18.2/0001-It-s-lpthread-not-lpthreads.patch
> > > +++ b/patches/perl-5.18.2/0001-It-s-lpthread-not-lpthreads.patch
> > > @@ -1,15 +1,20 @@
> > > From: Michael Olbrich <m.olbrich@pengutronix.de>
> > > Date: Wed, 23 Apr 2014 09:02:25 +0200
> > > Subject: [PATCH] It's -lpthread not -lpthreads
> > > +MIME-Version: 1.0
> > > +Content-Type: text/plain; charset=UTF-8
> > > +Content-Transfer-Encoding: 8bit
> >
> > Hmm, I wonder how you got these additional headers? :-)
> >
> > - Roland
>
>
> Git adds them, when you have signoff enabled globally in your
> gitconfig…
Not exactly. Git adds those on `git format-patch` if the commit
message in your patch contains other characters than 7 bit us-ascii.
In this case there's an 'ö' in the name in the s-o-b line. This is
also what happens if you recreate a patch series in ptxdist with
`git ptx-patches` and one of the commit messages contains stuff
encoded in utf-8 which does not fit in us-ascii.
You also get such lines if the content (not the commit message) of
your patch contains 8-bit chars and you send it with `git send-email`.
Git (2.20) does not add those lines to the patch on `git format-patch`
though.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-10-10 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 8:44 Björn Esser
2019-10-10 9:14 ` Uwe Kleine-König
2019-10-10 9:21 ` [ptxdist] [PATCH v2] " Björn Esser
2019-10-10 12:39 ` [ptxdist] [PATCH] " Roland Hieber
2019-10-10 12:45 ` Björn Esser
2019-10-10 13:25 ` Alexander Dahl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191010132504.hydcq7yitubjqag3@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=b.esser@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox