All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Woegerer, Paul" <Paul_Woegerer@mentor.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] lttng-ust: Update to version 2.3.0
Date: Wed, 4 Sep 2013 17:18:56 +0200	[thread overview]
Message-ID: <52274F60.5090603@mentor.com> (raw)
In-Reply-To: <CAP9ODKqZZtbthB479VE6Xeso47YUQmtLBbnN=cudDF0YKLe-rw@mail.gmail.com>

On 09/04/2013 05:10 PM, Otavio Salvador wrote:
> On Wed, Sep 4, 2013 at 9:51 AM, Woegerer, Paul <Paul_Woegerer@mentor.com> wrote:
>
> This kind of patch is nicer to send using -M option for format-patch
> so it tracks the renaming.
>
 
Thanks! I will keep that in mind for future submissions.

BTW, wouldn't it anyway make sense to change the recipes for lttng-ust,
lttng-ust, babeltrace to the same scheme as lttng-modules ? Then we
wouldn't need those nasty renaming anymore.

--
Best,
Paul

-- 
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division



  reply	other threads:[~2013-09-04 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 12:51 [PATCH 1/3] lttng-ust: Update to version 2.3.0 Woegerer, Paul
2013-09-04 15:10 ` Otavio Salvador
2013-09-04 15:18   ` Woegerer, Paul [this message]
2013-09-04 15:22     ` Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2013-09-05  9:00 [PATCH 0/3] lttng: update to lttng 2.3.0 Paul Woegerer
2013-09-05  9:00 ` [PATCH 1/3] lttng-ust: Update to version 2.3.0 Paul Woegerer
2013-09-05 12:56   ` Otavio Salvador

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=52274F60.5090603@mentor.com \
    --to=paul_woegerer@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=tom.zanussi@linux.intel.com \
    /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.