Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Marek Vasut <marex@denx.de>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 2/7] binutils: Repair nios2 PLT and GP handling
Date: Tue, 9 Feb 2016 11:00:11 -0500	[thread overview]
Message-ID: <56BA0D0B.60104@windriver.com> (raw)
In-Reply-To: <201602091529.17418.marex@denx.de>

On 2016-02-09 09:29 AM, Marek Vasut wrote:
> On Tuesday, February 09, 2016 at 03:21:17 PM, Burton, Ross wrote:
>> On 9 February 2016 at 13:08, Marek Vasut <marex@denx.de> wrote:
>>> Repair corner cases in nios2 PLT and GP handling. See the patches
>>> themselves for extensive detailed explanation.

This sentence doesn't really add much value since many patches
contain additional description and the logs here are mostly a
few lines from the ChangeLog which doesn't count as an extensive
detailed explanation in my books. :)

I expect that you're familiar with this but take a look at:
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Committing_your_patch

     Commit with a concise and descriptive message -
     one that explains your changes in a way others get
     a short overview without looking at the code.

>>>
>>> The patches don't contain the ChangeLog entries, since the changelog
>>> entries often cause trouble when applying the patch.

I'd prefer to see the ChangeLog snippets duplicated in the git log
so that it's easier to see what happened.

If you do a v2, please also mention that the patches are backports
since that's important to people when they consider whether the patch
should be accepted.

Thanks!

-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5


  reply	other threads:[~2016-02-09 16:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 11:31 [PATCH 1/7] strace: Fix build for arc, metag, nios2, or1k, tile Marek Vasut
2016-02-09 11:31 ` [PATCH 2/7] binutils: Repair nios2 PLT and GP handling Marek Vasut
2016-02-09 11:57   ` Burton, Ross
2016-02-09 13:08   ` [PATCH V2 " Marek Vasut
2016-02-09 14:21     ` Burton, Ross
2016-02-09 14:29       ` Marek Vasut
2016-02-09 16:00         ` Randy MacLeod [this message]
2016-02-09 16:52           ` Marek Vasut
2016-02-09 11:31 ` [PATCH 3/7] dpkg: Update to 1.18.4 Marek Vasut
2016-02-09 11:31 ` [PATCH 4/7] guile: Fix nios2 support Marek Vasut
2016-02-09 11:31 ` [PATCH 5/7] nspr: Add " Marek Vasut
2016-02-09 11:31 ` [PATCH 6/7] liburcu: " Marek Vasut
2016-02-09 11:53   ` Burton, Ross
2016-02-09 12:07     ` Marek Vasut
2016-02-09 13:24       ` Burton, Ross
2016-02-09 17:52       ` Khem Raj
2016-02-09 17:56         ` Marek Vasut
2016-02-10  9:05           ` Paul Eggleton
2016-02-10 11:58             ` Marek Vasut
2016-02-09 11:31 ` [PATCH 7/7] oprofile: " Marek Vasut
2016-02-09 11:51 ` [PATCH 1/7] strace: Fix build for arc, metag, nios2, or1k, tile Burton, Ross
2016-02-09 13:06   ` Marek Vasut
2016-02-09 13:07 ` [PATCH V2 " Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2016-02-10  0:04 Marek Vasut
2016-02-10  0:04 ` [PATCH V2 2/7] binutils: Repair nios2 PLT and GP handling Marek Vasut

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=56BA0D0B.60104@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox