Re: [PATCH] Re: .svnignore functionality

On Fri, Oct 19, 2001 at 03:46:05PM -0500, kfogel@collab.net wrote:
> Greg Stein <gstein@lyra.org> writes:
> > I second Brane's sarcasm here. We simply will *not* support files which
> > contain newlines in them.
> >
> > Thus, the one-per-line is the best option.
>
> Um, programmers (Makefile writers) aren't the only people who use
> version control systems.

And non-programmers are the *last* people to put a newline into their
filenames. I can't even begin to think how a non-programmer would do such a
thing.

Have you *ever* seen such a file? I sure haven't seen one in the twenty some
years I've been looking at filenames. Not even an accidental one. I did just
verify that it is possible (had to go into the Python cmdline to do it), but
seen one out in the wild? Nope.

> There are currently problems in Subversion which make versioning files
> with newlines in their names difficult, but that's not the same as a
> policy of not supporting them. We've not had such a policy before
> now, as far as I can remember, and (Greg's assertion notwithstanding)
> won't make such a policy without at least some discussion.

Set your policy however :-) ... I'm just voting. And mine is a big +1 on not
supporting newlines in filenames.

It isn't possible to veto a concept -- only code. But if the code to support
newlines is hairy... well :-)

> They can always be escaped ("\n") in things like status output,

Do you want to do all the work and maintain the stuff into the future? And
for what benefit? So we can *theoretically* support a case which nobody will
*actually* use?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org