MobileRead Forums - View Single Post - ct-ng is moving rapidly on, how do we keep it useful?

knc1 · 10-26-2012, 07:52 AM

Actually, both Buildroot and Crosstool-ng make it easy to keep a kernel version selection that has been dropped.

Just ask the repository manager (Buildroot == git, ct-ng == hg) for the changeset that took it out, then two choices:
Just revert that change, or
Hand enter it again.

Both projects are careful to keep such changes (version changes, of anything) compartmentalize as a single changeset.
The naming conventions are such that there should not be any name clashes, not even in the 'patch' directories.

Of course, you will probably want to name a local 'branch' of the main code stream before you do that. But local changes should be on a named 'branch' anyway.

10-26-2012, 07:52 AM	#2
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Kernel version Actually, both Buildroot and Crosstool-ng make it easy to keep a kernel version selection that has been dropped. Just ask the repository manager (Buildroot == git, ct-ng == hg) for the changeset that took it out, then two choices: Just revert that change, or Hand enter it again. Both projects are careful to keep such changes (version changes, of anything) compartmentalize as a single changeset. The naming conventions are such that there should not be any name clashes, not even in the 'patch' directories. Of course, you will probably want to name a local 'branch' of the main code stream before you do that. But local changes should be on a named 'branch' anyway.