< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
Best regards, Byron Campen
In terms of "cleaning up the svn artifacts," it's much easier to justuse "svn export". You can export from either the repository (i.e. usinga URL), or from a working directory. That said, I know for a fact that Byron has put together a tarfile for the 1.0 release. It would be a Really Bad Thing (from a proceduralperspective) to have two files, both purporting to be the "official" 1.0release, that differ in any way whatsoever.In other words: *please* coordinate with Byron before you make somethingavailable that claims to be an official 1.0 release tarball. If you absolutely *must* do something right now, then call my cell, and I'll see what I can do to put you in touch with Byron. /a Jason Fischl wrote:I updated the main resiprocate project page to have a pointer to the resiprocate-1.0 branch of subversion. Also, once we have a tarball, I will update freshmeat. Is producing a tarball a simple matter of tarring up the svn checkout and removing the svn artifacts? If so, I will do it today. Jason On 10/28/06, Jason Fischl <jason@xxxxxxxxxxxxxxx> wrote:I just visited this page: http://www.resiprocate.org which forwards to: http://www.sipfoundry.org/reSIProcate/ There is no obvious link to get to the tarball of resiprocate-1.0. If I click on Public Tarball Archives: https://www.sipfoundry.org/pub/resiprocate I get an invalid link. So where should this go? What is the link to the public tarball? Thanks Jason_______________________________________________ resiprocate-devel mailing list resiprocate-devel@xxxxxxxxxxxxxxxxxxx https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel_______________________________________________ resiprocate-devel mailing list resiprocate-devel@xxxxxxxxxxxxxxxxxxx https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
Attachment:
smime.p7s
Description: S/MIME cryptographic signature