I perceive that you've got a good technical background, so I hope you
will go back to the beginning of this discussion and read it again.
You are only arguing in circles. I alone have already addressed all
of your concerns thoroughly, and repeatedly while responding to
others. If you ever come up with a new argument that is not already
taken care of, please submit it. Otherwize, you are simply not
looking at the whole picture.
I do wish you had described a specific purpose that blank lines have
in Perl POD, yet it does not matter. We both already agree that you
cannot afford to mess with mixed styles on your unique application.
You are screwed in that case. We both agree.
As far as you implying "c" is the minority by not worrying about
changed newlines, you are totally unfounded. This POD thing you are
talking about is apparently aminority :) The common ones I refer to
are C and all c-like derevative languages, BASIC, Pascal, Perl, HTML,
XML (?), and uncounted other languages and markup formats that I
could think of in the next hour. Don't forget text documentation. I
certainly cannot picture someone crashing their installation because
of the wrong number of blank lines in the "INSTALL" doc they were
reading with any text viewer.
On Friday 02 February 2007 13:45, Frodak wrote:
> Sigh, SVN isn't stopping you. The client-side config
> settings don't effect how the repository is tracking
> the file. You have to set the file properties when
> importing or adding the file.
I know I only mean tries to stop me (by aborting). Shoot, no
programmable thing stops ME ;-) Still, you indicate you are missing
something about what the problem is. You seem so afraid that giving
me the option of handling text would interfere with your stuff--just
don't use the option.
If I guess right, you are still thinking that I should merrily
find/write an external tool to modify the vendor release files before
importing, right? But you yourself agree: *bad idea*. We should not
be modifying any files BEFORE importing to the revision control. It
loses "history". I am only asking that svn be allowed (as a user
option) to treat these known text-files as just what they are... text
files. It already does that with exception of mixed-styles--but only
because it does not know if I really want it. If I were so afraid of
it converting wrong, then I would not enable the option, just as you
don't have to. Again, please re-read at least my messages regarding
this discussion if not all the others saying why the request should
I think 'nough said for me, since there's no new concerns being
brought up. --jeffs
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Feb 2 22:48:53 2007