Roman Neuhauser <neuhauser@mobil.cz> writes:
> > You're absolutely correct. And thankfully, Subversion has no support
> > for commit emails, either. We do, however, have tools (external to
> > Subversion, mind you) and a good API that can assemble a commit mail
> > and dispatch it. Likewise, you could have a tool (again, external to
> > Subversion) that converts your line-endings back and forth for you.
>
> If SVN has an "API that can assemble a commit mail and dispatch it",
> then it has _support_ for commit mails. Or I don't know what support
> is. Mind you, I don't care a dime whether the EOL conversion is done
> by the svn client, server, or 10 lines of a shell script that you
> plug into either of those two.[1] I just beg for EOL conversion to be
> an option.
Sorry about that. My grammar got fudged when I pushed the
parenthetical expression stack. Allow me to rephrase.
We do, however, have an API that exposes things like revision
properties (which contains dates and authors and log messages) and
which will describe differences between version trees (useful for
determining what changed between two revisions). These are the
kinds of things used by the particular commit mail script found on
svn.collab.net, but are by all means not specifically related to
email whatsoever.
So yes, if by "supports commit mails" you mean that Subversion doesn't
explicitly prevent someone from assembing and dispatching a commit
mail, you're absolutely correct. And by the same token, "support" for
newline conversion is fully supported today (that is, Subversion
doesn't prevent someone from converting newline formats on the client
side).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006