Re: [dev] changing the patch mechanism for external sources

2009-01-26 Thread Hans-Joachim Lankenau
hi! Stephan Bergmann wrote: On 01/23/09 16:10, Hans-Joachim Lankenau wrote: with the changes done in the cws ause099, each change now will reside in its own patch. for the local module makefiles, the only visible change is PATCH_FILE_NAME -> PATCH_FILES. this variable now hold the list (and app

Re: [dev] changing the patch mechanism for external sources

2009-01-26 Thread Stephan Bergmann
On 01/23/09 16:10, Hans-Joachim Lankenau wrote: with the changes done in the cws ause099, each change now will reside in its own patch. for the local module makefiles, the only visible change is PATCH_FILE_NAME -> PATCH_FILES. this variable now hold the list (and apply prder) of the existing pat

Re: [dev] changing the patch mechanism for external sources

2009-01-24 Thread Caolán McNamara
On Fri, 2009-01-23 at 21:10 +0100, Pavel Janík wrote: > Do we need to define some naming scheme for patches or should we keep > the work of generating correct/random names to patchers? I'd suggest a scheme that includes the upstream bugtracker id that the patch was submitted upstream under, or t

Re: [dev] changing the patch mechanism for external sources

2009-01-23 Thread Pavel Janík
Hi, On 23.1.2009, at 16:10, Hans-Joachim Lankenau wrote: with the changes done in the cws ause099, each change now will reside in its own patch. for the local module makefiles, the only visible change is PATCH_FILE_NAME -> PATCH_FILES. this variable now hold the list (and apply prder) of

Re: [dev] changing the patch mechanism for external sources

2009-01-23 Thread Frank Schönheit - Sun Microsystems Germany
Hi Ause, > in the current scenario, there is only one active patch per source > tarball which has to contain all required changes for the build. as > discussed in issue 40246, this may lead to duplication and hard to > maintain patches. > > with the changes done in the cws ause099, each change no

Re: [dev] changing the patch mechanism for external sources

2009-01-23 Thread Caolán McNamara
On Fri, 2009-01-23 at 16:10 +0100, Hans-Joachim Lankenau wrote: > hi! > with the changes done in the cws ause099, each change now will reside in > its own patch. for the local module makefiles, the only visible change > is PATCH_FILE_NAME -> PATCH_FILES. this variable now hold the list (and > app

[dev] changing the patch mechanism for external sources

2009-01-23 Thread Hans-Joachim Lankenau
hi! in the current scenario, there is only one active patch per source tarball which has to contain all required changes for the build. as discussed in issue 40246, this may lead to duplication and hard to maintain patches. with the changes done in the cws ause099, each change now will reside in