All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: B29882@freescale.com, B19537@freescale.com
Subject: Re: [meta-networking v5 ] inetutils : Update to 1.9.1
Date: Mon, 19 Nov 2012 08:30:40 -0500	[thread overview]
Message-ID: <20121119133040.GB5534@windriver.com> (raw)
In-Reply-To: <CAP9ODKpfdpS3ULMNPig7d-n+2y5tvvvKmHi+1fP8UP+E=dqtDA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

[Re: [oe] [meta-networking v5 ] inetutils : Update to 1.9.1] On 12.11.19 (Mon 08:34) Otavio Salvador wrote:

> On Fri, Nov 16, 2012 at 12:00 AM, Chunrong Guo <b40290@freescale.com> wrote:
> 
> >   * There are difference spaces between  inetutils-1.8/COPYING
> >     and inetutils-1.9.1/COPYING,so md5sum is changed.
> >
> > Signed-off-by: Chunrong Guo <b40290@freescale.com>
> >
> 
> I did not built or tested it but the commit log might be improved to
> express what happened to the patches you removed. I assume they were fixed
> upstream but it is not clear looking at the changes or commit log.
> 
> Please make it explicit.

I agree.  I only got do to a proper build test yesterday, and all seemed
well, but I'd like to see the log expanded a bit as well.

Almost there!  And thanks for the update to the new version, that's
something I'd been thinking I was going to need to get to soon, so it's
saving me some time.

-- 
Joe MacDonald, Sr. Member of Technical Staff, Linux Products Group, Wind River
direct 613.270.5750     mobile 613.291.7421     fax 613.592.2283

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-11-19 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  2:00 [meta-networking v5 ] inetutils : Update to 1.9.1 Chunrong Guo
2012-11-19  7:35 ` chunrongguo
2012-11-19 10:34 ` Otavio Salvador
2012-11-19 13:30   ` Joe MacDonald [this message]
2012-11-20  5:53     ` chunrongguo

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=20121119133040.GB5534@windriver.com \
    --to=joe.macdonald@windriver.com \
    --cc=B19537@freescale.com \
    --cc=B29882@freescale.com \
    --cc=openembedded-devel@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.