All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH for-4.11] tools: set DEBUG_DIR from configure
Date: Mon, 28 May 2018 08:06:11 +0200	[thread overview]
Message-ID: <20180528060611.GA7595@aepfle.de> (raw)
In-Reply-To: <23304.12272.757552.289764@mariner.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 443 bytes --]

On Fri, May 25, Ian Jackson wrote:

> Can you please provide that information ?  That should really have
> been in your commit message, as the git commit id.  TBH, most of what
> is in that email could profitably have been in your commit message...

Perhaps 641f9ce2fa should have been more verbose.

Do you want me to provide a verbose backport, or would that be against
the rules of how backporting from master is supposed to be done?

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-28  6:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 16:13 [PATCH for-4.11] tools: set DEBUG_DIR from configure Roger Pau Monne
2018-03-27 16:18 ` Olaf Hering
2018-03-27 16:20   ` Roger Pau Monné
2018-03-27 16:28     ` Roger Pau Monné
2018-03-27 16:55       ` Doug Goldstein
2018-03-28  7:26         ` Roger Pau Monné
2018-03-28 16:27           ` Doug Goldstein
2018-05-25 15:19 ` Olaf Hering
2018-05-25 15:46   ` Ian Jackson
2018-05-28  6:06     ` Olaf Hering [this message]
2018-05-29 10:22       ` Ian Jackson

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=20180528060611.GA7595@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.