From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] connman: update to 0.78
Date: Fri, 09 Dec 2011 16:55:25 +0000 [thread overview]
Message-ID: <1323449725.5309.187.camel@ted> (raw)
In-Reply-To: <CAP9ODKpvAYr7e+9bS4Uyq8F_nsVdjoBchZPttqbcJGsoZDfCiQ@mail.gmail.com>
On Fri, 2011-12-09 at 14:38 -0200, Otavio Salvador wrote:
> On Fri, Dec 9, 2011 at 12:18, Richard Purdie:
>
> f) Reorder variables in the file so as to make the diff
> unreadable and
> hard to review
>
> This was indeed done and I am sorry but it does seems more easy to
> follow now.
In future please do this as a separate commit which just changes the
order. I will start just outright rejecting patches which combine code
changes and unrelated ordering changes since it makes the patches
unnecessarily hard to review.
> So all things considered, this kind of change is a nightmare
> to review
> in this form and the commit message only covers half the
> changes it
> makes. We need to do better than this...
>
>
> Not easy to accomplish as the difference between meta-oe and oe-core
> on this was huge. It could have been done better, sure ... and a v2
> patch will come shortly.
Thanks. I think the best way to improve this in future would be to keep
code changes and ordering (or whitespace) changes in separate commits
(and also enable rename detection on the change you send).
Cheers,
Richard
prev parent reply other threads:[~2011-12-09 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 10:51 [PATCH] connman: update to 0.78 Otavio Salvador
2011-12-09 14:18 ` Richard Purdie
2011-12-09 16:38 ` Otavio Salvador
2011-12-09 16:55 ` Richard Purdie [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=1323449725.5309.187.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 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.