Re: VMS support

[Dan Nicolaescu <dann@ics.uci.edu>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > > If you only can spend a few minutes at a time when doing this (and
  > > I do), you can't write ChangeLogs when doing the work because they
  > > will conflict on updates.
  > 
  > You should place the ChangeLog text somewhere where it won't conflict

[snip] 
Yes there are solutions to all these, but they mean just more work, and
mean changing the normal work style, which is equivalent to more work.

  > > On the other hand the gain is inexistent.
  > 
  > If someone ever intends to pick up this code and do something useful
  > with it, having it cleanly delimited by before/after tags is
  > very helpful.  If it's not commited as a single commit, you risk having
  > your change be interleaved with other unrelated changes.  Of course, if
  > nobody ever picks it up, the gain is indeed inexistent, but the cost
  > really seems pretty minor compared to the effort needed to figure out
  > how to remove the code (which parts to remove, etc...).

That's what I've been saying, its absolutely _not_ minor.  And trading
requiring to do work now for _maybe_ avoiding work in the future when
_maybe_ someone _might_ pick up the code is a bad tradeoff.

So the question is, will you continue this policy?