[asterisk-dev] Confused with release numbers, how to manage incremental patching ?

[Pavel Troller]

Hi!
  Sorry for reopening this stupid thread, but WHY THE HELL the patch for
asterisk-1.6.1.10 is based on 1.6.1.5 ?
  What should one do, when he carefully incorporates every patch into his
source tree (full of his own patches, so it's not easy to simply throw out
and start with a fresh download), he's now standing at 1.6.1.10-rc3 and
boom, a patch is based on a tree 5 releases back ???
  Is there a good soul capable of creating a patch from 1.6.1.10-rc3 to
1.6.1.10-final ? Similarly, as absolutely logical series of Linux kernel
patches (in the "incr" subdirectory of the main kernel directory)... This
policy makes asterisk patch files almost useless...

WIth regards,
   Pavel