On Fri, Jul 11, 2008 at 10:57 AM, Johan Vromans <[EMAIL PROTECTED]> wrote:
> But for all the individual modules that are part of a package? Their
> version numbers should only increase when something changed, i.e., at
> commit time. Not at release time. A task very neatly handled by CVS.
> And for which GIT c.s. has no alternative.

I disagree.  For one, as Elliot pointed out, it's a royal pain to
figure out which version of a module goes with which version of
another module in the same distro.  Also, multiple modules in the same
distro tend to depend on each other of course, so their functionality
can change in subtle or not-so-subtle ways even if their code doesn't.

I prefer slapping an identical version number on every .pm file in the
distribution.

 -Ken

Reply via email to