Robin H. Johnson wrote:
In my original email, I also suggested this solution, but it seems that nobody
read it:
] Alternatively, follow the example of any ebuild that uses a dated
] patchset, and just have the date of the patchset in the ebuild, and only
] increment $PR singly.
This solution already exists in MANY places in the tree, and should probably be
preferred over the long $PR or $RC values.
Yeah, except revisions are supposed to be for changes to ebuild code,
not upstream code.
This gets problematic for people trying to report bugs to upstream,
because they and upstream have no idea what code they're actually running.
Thanks,
Donnie
--
[EMAIL PROTECTED] mailing list
