mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <aar@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] iproute2 build errors when updating to 4.6
Date: Wed, 15 Jun 2016 20:37:10 +0200	[thread overview]
Message-ID: <c99278f7-458d-0627-246b-ae785d861123@pengutronix.de> (raw)
In-Reply-To: <20160530195958.GB25535@archie.localdomain>


Hi,

On 05/30/2016 09:59 PM, Clemens Gruber wrote:
> Hi,
> 
> On Sun, May 29, 2016 at 08:31:07PM +0200, Alexander Aring wrote:
>> I just sent the patch to netdev for iproute2 and cc you. If all is fine
>> from netdev people, do you want to send your work for iproute2 version
>> bump to mainline ptxdist?
> 
> Great!
> 
> Hm, I think you deserve the credit for the ptxdist change too! Also, I
> am not sure if we should add your patch to the patches directory or wait
> for upstream to fix it and delay the version bump until then?
> 

patch came upstream today, but I think it takes some time for new
release. What are the great new features in new iproute2 version?

I think it's fine to version bump + add patches for iproute2.

- Alex

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-06-15 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 23:55 Clemens Gruber
2016-05-24  7:20 ` Alexander Aring
2016-05-24  7:30   ` Alexander Aring
2016-05-24 13:01     ` Clemens Gruber
2016-05-24 15:24       ` Alexander Aring
2016-05-24 18:08         ` Alexander Aring
2016-05-25 17:42           ` Clemens Gruber
2016-05-29 18:31             ` Alexander Aring
2016-05-30 19:59               ` Clemens Gruber
2016-06-15 18:37                 ` Alexander Aring [this message]
2016-06-16 16:19                   ` Clemens Gruber
2016-05-24 10:04 ` Michael Olbrich

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=c99278f7-458d-0627-246b-ae785d861123@pengutronix.de \
    --to=aar@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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