Re: Incubator report is late!

2010-01-18 Thread Justin Erenkrantz
On Tue, Jan 19, 2010 at 3:01 AM, Hyrum K. Wright wrote: > On Jan 18, 2010, at 2:19 PM, Justin Erenkrantz wrote: > >> On Mon, Jan 18, 2010 at 4:56 PM, Hyrum K. Wright >> wrote: >>> My excuse is that I did it last month.  :) >>> >>> Actually, today is rototill-the-garden day, so the earliest I can

Re: TODO: Python bindings re-license

2010-01-18 Thread David James
2010/1/18 Роман Донченко : > Also note that I want to eventually remove the trac directory and integrate > non-duplicate tests from there into the "main" testsuite - albeit I'm not > sure if I'm allowed to do that. Maybe we can persuade Edgewall to formally > contribute those parts to ASF so we can

RE: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Julian Foad
Thanks for explaining! - Julian Kamesh Jayachandran wrote: > The patch is in concept complete(Yet to run through the testsuite and > to justify few cases by exercising those code base, which I will do > tomorrow) to make the indication of 'commit' operation via the new > header 'SVN-COMMIT'. Wit

Re: TODO: Python bindings re-license

2010-01-18 Thread Роман Донченко
C. Michael Pilato писал в своём письме Tue, 19 Jan 2010 01:10:26 +0300: We still have in our tree (currently at trunk/www/license-for-python-bindings.html, but likely to be moved elsewhere) a special license for the Subversion Python bindings. The document claims that the copyright for the b

Re: TODO: Python bindings re-license

2010-01-18 Thread Jeremy Whitlock
> I've not done much exploration here, but this seems odd to me. As far as I > remembered, our Python bindings don't use any Trac software at all. I > recall that we imported the Trac test framework some time ago, but I was > under the impression that this was a limited dependency -- that the bin

TODO: Python bindings re-license

2010-01-18 Thread C. Michael Pilato
We still have in our tree (currently at trunk/www/license-for-python-bindings.html, but likely to be moved elsewhere) a special license for the Subversion Python bindings. The document claims that the copyright for the bindings is dually held by CollabNet and by Edgewall (the folks behind Trac).

Re: Subversion in 2010

2010-01-18 Thread Joe Schaefer
- Original Message > From: Joe Schaefer > To: C. Michael Pilato > Cc: Karl Fogel ; Mark Mielke ; > Hyrum K. Wright ; Mark Phippard > ; Subversion Dev > Sent: Mon, January 18, 2010 3:51:48 PM > Subject: Re: Subversion in 2010 > > - Original Message > > > From: C. Michael Pi

Re: Subversion in 2010

2010-01-18 Thread Joe Schaefer
- Original Message > From: C. Michael Pilato > To: Joe Schaefer > Cc: Karl Fogel ; Mark Mielke ; > Hyrum K. Wright ; Mark Phippard > ; Subversion Dev > Sent: Mon, January 18, 2010 3:41:19 PM > Subject: Re: Subversion in 2010 > > For the sake of those that don't know, Joe is a member

Re: Subversion in 2010

2010-01-18 Thread C. Michael Pilato
For the sake of those that don't know, Joe is a member of the Apache Infrastructure team, where it becomes partly his responsibility to influence and support decisions about such things as which version control systems are available to projects hosted at Apache. I don't get the sense that he's mer

Re: Subversion in 2010

2010-01-18 Thread Joe Schaefer
- Original Message > From: Karl Fogel > To: Joe Schaefer > Cc: Mark Mielke ; Hyrum K. Wright > ; Mark Phippard ; > Subversion Dev > Sent: Mon, January 18, 2010 10:01:25 AM > Subject: Re: Subversion in 2010 > > Joe Schaefer writes: > >What I would like to see from this project is les

RE: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Kamesh Jayachandran
>whether it addresses any of the points Mike raised and in what ways, >that sort of thing. Hey forgot to answer this bit. Mike was suggesting to make use of 'DAV:apply-to-version' in CHECKOUT rather than the problematic PROPFIND. I did not explore this bit yet. With regards Kamesh Jayachandran

RE: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Kamesh Jayachandran
>Sorry, Kamesh, that wasn't a very helpful question. >I know the aim is to to fix the problem that occurs during a commit >through a proxy server - that's the one-line overview. I know the patch >adds new parameters to a bunch of functions and sets them to particular >values and such like - I can

RE: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Kamesh Jayachandran
>Hi Kamesh. >What does this patch do? It adds the magical header 'SVN-COMMIT' for PROPFIND calls associated with a commit operation over neon. Server catches this magical header and decides whether to proxy or not. As I mentioned already we need to do this only for neon as serf do not make P

Re: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Julian Foad
I (Julian Foad) wrote: > Kamesh Jayachandran wrote: > > Attached patch just fixes this at ra_neon layer alone(ra_serf do not > > need the fix at least on trunk, as it do not use the PROPFIND for this > > rather uses POST which do not suffer from this issue as it simply > > proxies to MASTER). >

Incubator report is late!

2010-01-18 Thread C. Michael Pilato
[Posting on the correct list this time.] Just noting that our January Incubator report is late. Who's claiming ownership of that responsibility? -- C. Michael Pilato CollabNet <> www.collab.net <> Distributed Development On Demand signature.asc Description: OpenPGP digital signature

Re: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Julian Foad
Kamesh Jayachandran wrote: > Attached patch just fixes this at ra_neon layer alone(ra_serf do not > need the fix at least on trunk, as it do not use the PROPFIND for this > rather uses POST which do not suffer from this issue as it simply > proxies to MASTER). Hi Kamesh. What does this patch d

Re: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV) Version 2

2010-01-18 Thread Kamesh Jayachandran
On 01/13/2010 05:07 PM, Kamesh Jayachandran wrote: On 01/13/2010 12:08 AM, C. Michael Pilato wrote: Kamesh Jayachandran wrote: Hi All, Last week I posted the patch to implement 'svn client' to identify the svn operation they are about to do with a given ra_session. Following thread has the de

Re: Subversion in 2010

2010-01-18 Thread Karl Fogel
Joe Schaefer writes: >What I would like to see from this project is less arguing >about irrelevant concepts and more features in the working >copy, ideally to make fewer network trips for better performance >or to support queued commits so sysadmins need not panic over >work stoppages due the the

RE: libsvn_wc bug: pristine contents for locally replaced file

2010-01-18 Thread Bert Huijben
> -Original Message- > From: Neels J Hofmeyr [mailto:ne...@elego.de] > Sent: maandag 18 januari 2010 14:16 > To: Julian Foad > Cc: Bert Huijben; dev@subversion.apache.org > Subject: Re: libsvn_wc bug: pristine contents for locally replaced file > > >> Bert Huijben wrote: > >>> Currently

RE: [PATCH] Fix #3544 - svn update does not restore excluded files

2010-01-18 Thread Bert Huijben
> -Original Message- > From: Kannan [mailto:kann...@collab.net] > Sent: maandag 18 januari 2010 5:46 > To: C. Michael Pilato > Cc: Philip Martin; SVN Dev > Subject: Re: [PATCH] Fix #3544 - svn update does not restore excluded files > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > >

Re: libsvn_wc bug: pristine contents for locally replaced file

2010-01-18 Thread Neels J Hofmeyr
>> Bert Huijben wrote: >>> Currently @BASE is the 'previous' version of the node that will be >>> committed. For added and replaced nodes with history there is no @BASE. [...] Julian Foad wrote: > I always thought (and still think) that, from the user's point of view, > "base" always meant "the ver

Re: libsvn_wc bug: pristine contents for locally replaced file

2010-01-18 Thread Julian Foad
Neels J Hofmeyr wrote: > Bert Huijben wrote: > > I'm not sure if it needs fixing. It probably needs a better explanation on > > what @BASE is and isn't. > > > > Currently @BASE is the 'previous' version of the node that will be > > committed. For added and replaced nodes with history there is no @