Hi. I just renamed kernel configs corresponding to kernel minor version, not kernel release (in this case - *-4.1.13-* to *-4.1-*).
Storing kernel revision in config name IMHO is useless; kernels usually doesn't provide any new config variables in fresh bugfix releases (I can't remember such cases), but kernel update adds useless configs renaming actions. 30.11.2015 00:23, Erich Titl пишет: > Hi Andrew > > What exactly will this change and why is it necessary? > > Thanks > > ET > > -------- Weitergeleitete Nachricht -------- > Betreff: [leaf:bering-uclibc] New commit by Andrew Denisenko > Datum: Sun, 29 Nov 2015 22:20:56 +0000 > Von: LEAF Linux Embedded Appliance Framework Git repository > <nore...@bering-uclibc.leaf.p.re.sf.net> > Antwort an: LEAF Linux Embedded Appliance Framework Git repository > <nore...@bering-uclibc.leaf.p.re.sf.net> > An: LEAF Linux Embedded Appliance Framework Git repository > <nore...@bering-uclibc.leaf.p.re.sf.net> > > > > Branch: master > > linux: use branch name instead of release name for kernel configs > > By Andrew Denisenko on 11/29/2015 22:19 > *View Changes* > <http://sourceforge.net/p/leaf/bering-uclibc/ci/21287b803c46518f1be6589eb7c3fd8de7f958d6/> > > ------------------------------------------------------------------------ > > Sent from sourceforge.net because you indicated interest in > https://sourceforge.net/p/leaf/bering-uclibc/ > > To unsubscribe from further messages, please visit > https://sourceforge.net/auth/subscriptions/ > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------------------------------ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
