-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/24/13 5:16 PM, Xyne wrote:
Greg Larkin wrote:
Hi Xyne,
Thanks for turning that around so quickly, and I am doing some
testing here with the idea to incorporate svn-export into the
FreeBSD ports tree.
I've run into a couple of problems
Greg Larkin wrote:
# python3 svn-export -r 31
http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt
Exporting new repository.
Exported revision 31
# python3 svn-export --revision-file rev.dat
http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt
Determining current revision.
Current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/25/13 1:53 PM, Xyne wrote:
Greg Larkin wrote:
# python3 svn-export -r 31
http://svn.freebsd.org/ports/head/ports-mgmt ports-mgmt Exporting
new repository. Exported revision 31 # python3 svn-export
--revision-file rev.dat
Greg Larkin wrote:
Hi Xyne,
Thanks for turning that around so quickly, and I am doing some testing
here with the idea to incorporate svn-export into the FreeBSD ports tree.
I've run into a couple of problems that I hope you can take a look at it:
- - Changesets containing directory or file
Hello.
2013/01/18 23:50:17 + Xyne x...@archlinux.ca = To Warren Block :
X On 2013-01-17 21:32 -0700
X Warren Block wrote:
X
X A working version in any language would be great. A better version in
X Python would be nice, too, but it's the working part that's important.
X
X There's a
On Sat, 19 Jan 2013, Xyne wrote:
svn-export has now been rewritten in Python 3. Here's a quick list of
changes/features:
* threads have been replaced with forks (and remain optional)
* new option to set svn binary
* new option to generate shell script instead of using internal calls
* no
Hello.
2013/01/17 21:32:08 -0700 Warren Block wbl...@wonkity.com = To Xyne :
WB On Fri, 18 Jan 2013, Xyne wrote:
WB
WB I'm the author of svn-export. I haven't really touched the code since I
wrote
WB it in 2009 and back then I tended to write most things in noobish Perl.
I shouldn't name
On 2013-01-17 21:32 -0700
Warren Block wrote:
A working version in any language would be great. A better version in
Python would be nice, too, but it's the working part that's important.
There's a difference between working and working on a random system with
unexpectedly disabled features.
Hi,
svn-export has now been rewritten in Python 3. Here's a quick list of
changes/features:
* threads have been replaced with forks (and remain optional)
* new option to set svn binary
* new option to generate shell script instead of using internal calls
* no subshell invocation
* only svn
Peter Vereshagin wrote:
I believe 'amd64' is the common architecture these days and 'perl malloc' is
the
feature needed for profiling and/or leaks detection.
Good news is that such a stuff can be redone with forks instead of threads but
it should take me the time amount I'm not supposed to have
On Fri, 18 Jan 2013, Xyne wrote:
I'm the author of svn-export. I haven't really touched the code since I wrote
it in 2009 and back then I tended to write most things in noobish Perl.
Although it should not be difficult to replace threading with forking (and I
agree that Perl threading is
Hello.
2013/01/16 15:24:00 -0500 Greg Larkin glar...@freebsd.org = To Peter
Vereshagin :
GL On 1/16/13 3:07 PM, Peter Vereshagin wrote:
GL 2013/01/16 13:51:42 -0600 Joseph A. Nagy, Jr
GL jnagyjr1...@gmail.com = To Peter Vereshagin : JANJ On 01/16/13
GL 13:35, Peter Vereshagin wrote: JANJ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/13 3:55 PM, Peter Vereshagin wrote:
Hello.
2013/01/16 15:24:00 -0500 Greg Larkin glar...@freebsd.org = To
Peter Vereshagin : GL On 1/16/13 3:07 PM, Peter Vereshagin wrote:
GL 2013/01/16 13:51:42 -0600 Joseph A. Nagy, Jr GL
Hello.
2013/01/17 00:55:33 +0400 Peter Vereshagin pe...@vereshagin.org = To
freebsd-questions@freebsd.org :
PV GL If anyone wants to create a port for svn-export and send it my way for
PV GL review, I would be happy to do that. Otherwise, I expect to have a
PV GL look myself within the next few
14 matches
Mail list logo
