[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: RFC: Newline conversion in log messages and special props

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-09-06 20:01:05 CEST

> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> Branko Čibej <brane@xbc.nu> writes:
> > Proposal: When converting log messages to UTF-8, also convert
> > endings to LF. Conversely, when converting log messages to the
> > locale encoding (for $EDITOR or for display purposes), also
> > line endings to the native form.
> >
> > I think some of the special properties should get similar treatment:
> >
> > * Line-based textual properties: svn:ignore, svn:externals
> > * Whitespace-separated textual properties: svn:keywords
> >
> > While we're at it, perhaps we should also strip all whitespace from
> > keyword-like properties: svn:eol-style and svn:mime-type. I seem to
> > recall that we already had problem reports because a newline found
> > way into svn:mime-type.
> +1 on all of this.

> > I think that leaves svn:executable, which I don't care about so
> > much. It might make sense to only allow empty contents on that prop
> > since it's a boolean -- only its existence matters, not the contents
> > -- but that's more an aesthetic than a usability issue.

Handle it as a special case in the argument handling phase for "svn
svn:executable is a Subversion owned property.

I don't suppose you'll fall for that though.

Alternatively, "svn +x <WCTarget>"/"svn -x <WCTarget>" would also do the

If the interface gets awkward, it usually means you need to examine if
you're using the wrong interface. ;)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 6 20:01:43 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.