arch lists and patch set format

Thanks for indulging earlier arch related traffic on this list.

There are now some arch-specific mailing lists (subscription addresses
in brackets) where such traffic should be directed in the future.

        arch-users[-request]@regexps.com
        bug-arch[-request]@regexps.com
        arch-announce[-request]@regexps.com

There's a new release that fixes the first round of reported porting
problems, see www.regexps.com.

Re common patch set format: when/if its time to design a "standard", I
think the discussion between Zack and I illustrates the futility of
starting with syntax rather than semantics. The earnest design
process would do well to start with a consideration of what
information needs to be (somehow) represented in a (generalized)
patch, and precisely what that information means -- e.g. how to
interpret it as either an exact or inexact patch. With the semantics
worked out that way, all representations, XML, shell scripts, trees of
plain text, etc. will be isomorphic and inter-convertible, trivially
(by scripts, of course :-)

Re patch set syntax: Although he might disagree, I think Zack and I
agree about more than we disagree about.

-t

---------------------------------------------------------------------
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:57 2006