mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2] ppp: version bump 2.4.5 -> 2.4.7
Date: Fri, 21 Apr 2017 16:11:08 +0200	[thread overview]
Message-ID: <20170421141108.grxwoowxyb3njstj@lenoch> (raw)
In-Reply-To: <20170421130237.k3vdy6u2ct4xrgnv@pengutronix.de>

On Fri, Apr 21, 2017 at 03:02:37PM +0200, Michael Olbrich wrote:
> On Wed, Apr 12, 2017 at 10:30:51PM +0200, Ladislav Michl wrote:
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > ---
> >  Changes:
> >  - v2: Add forgotten 0030-no_crypt_hack.patch 
> > 
> >  Note: patches were not refreshed and renumbered as it
> >  would make review more difficult. I'm ready to send
> >  v3, eventually. 
> 
> I assume, the removed patches are included in the new version?

Yes, all dropped patches are present in mainline.

> If you create the patch with '-M' then renamed files are detected and can
> be reviewed sanely.

Ok, will use that when generating new version.

> mkl: You added these patches initially. Where are those from? Debian? Maybe
> we should check there for new versions.

I checked Debian when doing update and not all patches comes from there.
This is list of debian patches against 2.4.7:
  857 pro  4  2015 010_scripts_README.diff
 4786 pro 30  2015 011_scripts_redialer.diff
 2901 pro  4  2015 018_ip-up_option.diff
 2070 pro  4  2015 adaptive_echos
  958 pro  4  2015 chat_man
11144 led 27  2016 cifdefroute.dif 
 1144 pro 30  2015 close_dev_ppp
 1177 pro 30  2015 fix_linkpidfile 
  682 lis 11 12:48 fix-rp-pppoe-ftbfs.patch 
 2090 pro 30  2015 ipv6-accept-remote  
 7376 pro 30  2015 makefiles_cleanup
 1255 pro  4  2015 no_crypt_hack
 5133 pro  4  2015 ppp-2.3.11-oedod.dif
 6173 led 27  2016 ppp-2.4.2-ifname.diff
 1018 pro  4  2015 ppp-2.4.2-stripMSdomain
 1222 led 27  2016 ppp-2.4.4-strncatfix.patch
  932 led 27  2016 pppd-soname-hack.patch
  868 pro  4  2015 pppdump_use_zlib 
 2186 pro  4  2015 pppoatm_cleanup  
 2584 pro  4  2015 pppoatm_resolver_light
  277 pro  4  2015 pppoe_noads 
10740 čen 29  2016 pr-28-pppoe-custom-host-uniq-tag.patch
 1116 led 27  2016 radius-config.c-unkown-typo
  868 pro  4  2015 radius_mtu
  776 pro  4  2015 rc_mksid-no-buffer-overflow
  434 pro  4  2015 readable_connerrs
  276 pro  4  2015 resolv.conf_no_log  
  637 led 27  2016 secure-card-interpreter-fix
  735 lis 11 12:18 series  
  698 pro  4  2015 setenv_call_file 
 1623 pro  4  2015 zzz_config

Best regards,
	ladis

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2017-04-21 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 22:12 [ptxdist] [PATCH] " Ladislav Michl
2017-04-06  9:26 ` [ptxdist] get SVN folder ( without .tar extension) Pedro Lafuente
2017-04-06 11:55   ` Roland Hieber
2017-04-06 12:01     ` Roland Hieber
2017-04-07  9:28     ` Guillermo Rodriguez Garcia
2017-04-12 20:30 ` [ptxdist] [PATCH v2] ppp: version bump 2.4.5 -> 2.4.7 Ladislav Michl
2017-04-21 13:02   ` Michael Olbrich
2017-04-21 14:11     ` Ladislav Michl [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=20170421141108.grxwoowxyb3njstj@lenoch \
    --to=ladis@linux-mips.org \
    --cc=mkl@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