public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Ulf Hermann <ulf.hermann@qt.io>,
	"elfutils-devel@sourceware.org"	 <elfutils-devel@sourceware.org>
Subject: Re: [PATCH] Skip run-readelf-compressed.sh test if built without bzip2
Date: Wed, 16 Jan 2019 16:25:00 -0000	[thread overview]
Message-ID: <92143e775192a6755f22c196a3248dc0867c3400.camel@klomp.org> (raw)
In-Reply-To: <6f51f9c8-fa73-9689-3717-0aef90ec39d9@qt.io>

On Mon, 2019-01-14 at 08:27 +0000, Ulf Hermann wrote:
> > Added a ChangeLog and pushed to master.
> > Please don't sent patches with base64 encoding.
> > That make it really hard to apply them with git am.
> 
> Thanks, and sorry. As the message in my "Sent" folder is plain text with 
> 7bit encoding, it seems that something in between has re-encoded it (or 
> that thunderbird is lying to me).
> 
> As this is a repeating theme here, it might be a good idea to add an 
> option to submit patches in a less fragile way than inline in email. But 
> then, maybe that's just my particularly annoying combination of 
> thunderbird client and outlook server that keeps messing things up.

It might just be git am. It does display fine in my mua too, it is just
git am doesn't seem to like the raw message:

https://sourceware.org/cgi-bin/get-raw-msg?listname=elfutils-devel&date=2019-q1&msgid=67ff4de2-fd5a-0ba8-0b5d-173c5619a88b%40qt.io

But please do feel free to post patches as pull requests using git
request-pull -p if you have a public git repo (but please use -p and
also sent the output to the list to make reviewing easier).

Cheers,

Mark

  reply	other threads:[~2019-01-16 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 13:31 Ulf Hermann
2019-01-13 22:23 ` Mark Wielaard
2019-01-14  8:27   ` Ulf Hermann
2019-01-16 16:25     ` Mark Wielaard [this message]
2019-01-16 17:08       ` Frank Ch. Eigler

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=92143e775192a6755f22c196a3248dc0867c3400.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ulf.hermann@qt.io \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).