-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Imre, thanks for your fast reply.
I find it more comfortable to have separate configs and patch folders. So while trying to get a new kernel running (like 2.6.32, which currently gives me seg faults), you can easily switch back to the current stable kernel by just editing a single "Makefile". Very helpful to see if the problems are caused by the new kernel or the current package. After the new kernel became stable of course the old config and patches folder should be removed. I think that issue comes down to personal flavour, so maybe the OpenWrt team should define what is the preferred way. Thanks for your insight Maddes On 03.02.2010 12:29, Imre Kaloz wrote: > Hello, > > NAK. Although some people love to name the config files that way if the > differences > don't conflict, it makes no sense -- it's easier to keep the same config > and add the > extra symbols to it for the newer kernel. Also, if 2.6.32 is working, > there's no reason > to keep .30 around. > > > Imre > > > On Tue, 02 Feb 2010 20:28:22 +0100, Matthias Buecher / Germany > <[email protected]> wrote: > > Hello, > > please execute the following svn commands inside trunk to correct the > names of the orion config file and patches folder: > > svn mv target/linux/orion/config-default > target/linux/orion/config-2.6.30 > > svn mv target/linux/orion/patches/ target/linux/orion/patches-2.6.30/ > > Could any OpenWrt developer do this? kaloz? anyone? > > > [orion] move 2.6.30 configuration and patches to their appropriate names > > Signed-off by: Matthias Buecher <[email protected]> > > -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktpjNAACgkQUXXT+9wZdbXctQCfZGHM4SDo0YcSRakegmB8vhew EFEAn0oB3uhqAxleiYY0K7U5ZnuWu/fp =tRDh -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
