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

Re: sha-256 comment in /trunk/subversion/libsvn_subr/crypto.c

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 9 Jan 2013 09:39:49 -0500

On 01/08/2013 07:53 PM, Ben Reser wrote:
> In this case I think this code should probably be removed from trunk
> for the time being. The wiki for this functionality mentions that it
> may complicate our export control status. If we're not using it we
> should probably remove it prior to 1.8 branching. We can put it back
> later if we're ready to use it.

My state concern about our export status has, IIRC, been refuted. But I
need to find documentation of that refutation, and then remember to update
the wiki.

Removing the code from trunk is fine, I suppose -- just means that when I
next update my branch a bunch of supporting code will get blown away there,
forcing me to re-add it. But that's no big deal. That kind of churn seems
a bit unnecessary -- it is private, unused code after all.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2013-01-09 15:40:36 CET

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.