Re: CHANGES (take 2)

>>>>> On 3 Jul 2003, "Ben" == Ben Collins-Sussman wrote:

  Ben> I bet 50% of that verbiage is kfogel describing all the changes
  Ben> to cvs2svn.py, the stuff that's not important enough to
  Ben> mention. :-)

Upon looking at the logs, I actually noticed that the exact commits
Karl didn't want taking up space in the CHANGES file also had the
longest log messages. Which is why I originally included them :)

But I also see his point that a) he's the only one really working on
this stuff, and b) it's not really visible to anyone yet.

  Ben> In general, it's really hard to measure "code flux", and I
  Ben> don't like trying to do so.

Fair enough, and I agree. I was just trying to figure out why I came
up with so much for this release. It's always possible that any
given release can have very few commits but happen to be tremedously
visible/important while another can have a huge number of commits on
invisible/unimportant stuff. Of course, commits with extremely long
and detailed log messages certainly *seem* to be important to the
un-aware :)

>>>>> On 3 Jul 2003, "Ben" == Ben Collins-Sussman wrote:

  Ben> I really like the fact that you've started a "new tradition":
  Ben> including revision numbers next to each bullet.

  Ben> But in the process, you've also lost a tradition:

  Ben> I'd rather not substitute revision numbers for issue numbers.
  Ben> Have both, if possible.

I'll gladly attempt to have both where possible. The rev number is
obviously easily attainable, whereas the issue number is not unless
the committer mentions it in the log.

Incidently, the 'new' tradition was a complete accident. I didn't
realize the (#xxxx) was an issue number, and thought it was a rev
number being cross-referenced. It then dawned on me when I saw one
commit which said 'blah blah issue (#xxxx)' :)

-- 
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org