Re: svn commit: r1780191 - /subversion/site/publish/docs/release-notes/1.10.html

On Wed, Jan 25, 2017 at 3:41 PM, wrote: > Author: stsp > Date: Wed Jan 25 14:41:03 2017 > New Revision: 1780191 > > URL: http://svn.apache.org/viewvc?rev=1780191=rev > Log: > * release-notes/1.10.html: Add a section about the new conflict resolver. ... > + > + > +operation

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

On Tue, Jan 24, 2017 at 12:20 PM, Stefan Sperling wrote: > Hi, > > Another update on the new conflict resolver: > > We have 36 conflict resolver tests, all of which PASS. > I have updated the wiki page about conflict tests accordingly: >

Re: svn commit: r1783953 - /subversion/site/publish/docs/release-notes/1.10.html

On Wed, Feb 22, 2017 at 1:01 PM, Bert Huijben wrote: >> -Original Message- >> From: jcor...@apache.org [mailto:jcor...@apache.org] >> Sent: dinsdag 21 februari 2017 23:35 >> To: comm...@subversion.apache.org >> Subject: svn commit: r1783953 -

Re: svn commit: r1783790 - /subversion/site/publish/docs/release-notes/1.10.html

On Mon, Feb 20, 2017 at 8:50 PM, wrote: > Author: jcorvel > Date: Mon Feb 20 19:50:38 2017 > New Revision: 1783790 > > URL: http://svn.apache.org/viewvc?rev=1783790=rev > Log: > * publish/docs/release-notes/1.10.html: put "keep working copy state" as >resolution option

Re: 1.10.0-alpha1 is up for signing

On Thu, Feb 16, 2017 at 3:26 PM, Stefan Sperling wrote: > The 1.10.1-alpha1 release is finally up for signing. > > Full committers, please get this release from > https://dist.apache.org/repos/dist/dev/subversion > and add your signatures there. > > Thank you! Summary --- +1

Re: New MaxSVN releases (incl. 1.8.17 and 1.9.5)

On Fri, Feb 24, 2017 at 2:43 AM, Stefan wrote: ... > Please note that normally we'd have shipped this version with OpenSSL > 1.1.0c. However, we decided to postpone an upgrade to OpenSSL 1.1.0 for > the time being due to Apache httpd not having a compatible release > available

Re: 1.10.0-alpha2 is up for signing

On Fri, Feb 24, 2017 at 3:39 AM, Stefan wrote: > On 2/21/2017 13:54, Stefan Sperling wrote: >> The new 1.10.1-alpha2 release is up for signing. >> >> The proposed 1.10.0-alpha1 release had a compilation problem on Windows. >> The alpha2 release should fix this problem. It is

Re: 1.10.0-alpha2 is up for signing

On Tue, Feb 21, 2017 at 1:54 PM, Stefan Sperling wrote: > The new 1.10.1-alpha2 release is up for signing. > > The proposed 1.10.0-alpha1 release had a compilation problem on Windows. > The alpha2 release should fix this problem. It is based on trunk@r1783880. > > Full

Re: 1.10.0-alpha1 is up for signing

On Tue, Feb 21, 2017 at 5:29 PM, wrote: > If you compare this problem to 1.7 or something it wouldn’t be a regression. > > > > MSBuild by default builds all targets in the makefile, if you don’t pass a > target via the optional -t argument. In those older versions we always >

Re: svn commit: r1783790 - /subversion/site/publish/docs/release-notes/1.10.html

On Tue, Feb 21, 2017 at 12:24 PM, Stefan Sperling <s...@apache.org> wrote: > On Mon, Feb 20, 2017 at 08:57:24PM +0100, Johan Corveleyn wrote: >> Am I right that the same goes for "delete file" (local change) and >> "edit file" (incoming change)? If

Re: backport.pl now running on svn-qavm3

On Sat, Oct 8, 2016 at 12:19 AM, Greg Stein <gst...@gmail.com> wrote: > > > On Fri, Oct 7, 2016 at 11:34 AM, Daniel Shahaf <danie...@apache.org> wrote: >> >> Johan Corveleyn wrote on Fri, Oct 07, 2016 at 16:59:50 +0200: >> > Just a quick heads-u

Re: Your project VM needs to be migrated.

>> Additional help is certainly welcome. For starters, we'll need a >> recent svn build (perhaps simply our latest official release, 1.9.4) >> on there for the svn-role activities. I have no experience building >> svn on Linux. I can probably manage when starting from INSTALL, but >> I'm sure

Re: Your project VM needs to be migrated.

On Mon, Sep 26, 2016 at 8:33 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Johan Corveleyn wrote on Wed, Jul 27, 2016 at 17:00:26 +0200: >> On Wed, Jul 27, 2016 at 4:36 PM, Daniel Shahaf <d...@daniel.shahaf.name> >> wrote: >> > Daniel Shahaf wrote on

Re: svn commit: r1764536 - /subversion/branches/1.9.x/STATUS

On Wed, Oct 12, 2016 at 10:13 PM, wrote: > > Author: ivan > Date: Wed Oct 12 20:13:24 2016 > New Revision: 1764536 > > URL: http://svn.apache.org/viewvc?rev=1764536=rev > Log: > * STATUS: Veto r1759116 group. > > Modified: > subversion/branches/1.9.x/STATUS ... > @@ -135,6

Re: Migrating our wiki

On Sun, Oct 23, 2016 at 6:25 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Johan Corveleyn wrote on Sun, Oct 23, 2016 at 16:36:58 +0200: >> I can't take it any longer ... our (MoinMoin) wiki [1] is so slow that >> it's almost unusable. [,..] So I'd like us to move t

Migrating our wiki

I can't take it any longer ... our (MoinMoin) wiki [1] is so slow that it's almost unusable. For reading / browsing it's still more or less okay, but for editing it's not. It takes almost 5 minutes for me to save any change. We're not the first to run into this: in INFRA-12283 [2] a similar

Re: svn:auto-props: property specified in a parent dir but not specified in a subdir

dev@; please reply to dev@ only ] > > Johan Corveleyn wrote on Sat, Oct 15, 2016 at 22:59:28 +0200: > > C:\autoprops\wc\trunk\dir>svn pg svn:auto-props --show-inherited-props > > C:\autoprops\wc - *.txt = svn:eol-style=native > > > > C:\autoprops\wc\trunk - *

Re: Migrating our wiki

On Sun, Oct 23, 2016 at 10:11 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Sun, Oct 23, 2016 at 6:25 PM, Daniel Shahaf <d...@daniel.shahaf.name> > wrote: >> Johan Corveleyn wrote on Sun, Oct 23, 2016 at 16:36:58 +0200: >>> I can't take it any longer ... o

Re: svn:auto-props: property specified in a parent dir but not specified in a subdir

On Tue, Oct 18, 2016 at 1:35 PM, Daniel Shahaf wrote: > Branko Čibej wrote on Tue, Oct 18, 2016 at 13:08:37 +0200: >> It is. I don't think there's any way we can /not/ make it backwards >> incompatible, given the current implementation. Which is why I think we >> should

Re: 1.8.17 up for signing/testing

On Mon, Nov 21, 2016 at 4:30 PM, Evgeny Kotkov wrote: > The 1.8.17 release artifacts are now available for testing/signing. > Please get the tarballs from > https://dist.apache.org/repos/dist/dev/subversion > and add your signatures there. I plan to try and release

Re: 1.9.5 up for signing/testing

On Mon, Nov 21, 2016 at 4:30 PM, Evgeny Kotkov wrote: > The 1.9.5 release artifacts are now available for testing/signing. > Please get the tarballs from > https://dist.apache.org/repos/dist/dev/subversion > and add your signatures there. I plan to try and release

Re: Stop backport.pl running as cronjob? (was Re: svn commit: r1764631 - /subversion/branches/1.9.x-r1721488/)

Great, thanks Daniel! -- Johan On Fri, Oct 21, 2016 at 1:45 AM, Daniel Shahaf wrote: > Daniel Shahaf wrote on Thu, Oct 13, 2016 at 14:57:16 +: >> [[[ >> backport.py: Fix a race condition involving concurrent commits to STATUS >> (see r1764633). >> >> The fix is to

Re: Migrating our wiki

On Tue, Oct 25, 2016 at 2:37 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Sun, Oct 23, 2016 at 10:11 PM, Johan Corveleyn <jcor...@gmail.com> wrote: >> On Sun, Oct 23, 2016 at 6:25 PM, Daniel Shahaf <d...@daniel.shahaf.name> >> wrote: >>> Johan Cor

Re: [PATCH v2] Reject checkouts to existing directory

On Fri, Oct 28, 2016 at 10:34 AM, Patrick Steinhardt wrote: > On Fri, Oct 28, 2016 at 12:34:44AM +0200, Stefan wrote: >> On 10/27/2016 21:45, Stefan Sperling wrote: >> > On Tue, Oct 18, 2016 at 02:22:25PM +0200, Patrick Steinhardt wrote: >> >> Hi, >> >> >> >>

Re: Backport mixup last night

On Thu, Oct 13, 2016 at 4:17 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Johan Corveleyn wrote on Thu, Oct 13, 2016 at 11:37:25 +0200: >> [...] the cronjob of backport.pl was running simultaneously on >> svn-qavm2 (old machine) and svn-qavm3 (new machine we're mi

Backport mixup last night

Just a quick report about what happened and what I've done (things are okay now). There was an svn-role (automatic backport) mixup last night: some revisions were still correct, but the last 6 automated backport commits were wrong (mixed STATUS changes with wrong actual changes etc). Cause: the

Re: Stop backport.pl running as cronjob? (was Re: svn commit: r1764631 - /subversion/branches/1.9.x-r1721488/)

On Thu, Oct 13, 2016 at 1:05 PM, Branko Čibej wrote: > On 13.10.2016 13:01, Branko Čibej wrote: >> On 13.10.2016 11:39, Ivan Zhakov wrote: >>> On 13 October 2016 at 10:59, wrote: Author: jcorvel Date: Thu Oct 13 08:59:07 2016 New Revision:

Re: svn commit: r1764536 - /subversion/branches/1.9.x/STATUS

On Thu, Oct 13, 2016 at 1:22 PM, Ivan Zhakov <i...@apache.org> wrote: > On 12 October 2016 at 22:30, Johan Corveleyn <jcor...@gmail.com> wrote: >> On Wed, Oct 12, 2016 at 10:13 PM, <i...@apache.org> wrote: >>> >>> Author: ivan >>> Da

Re: svn commit: r1765088 - in /subversion/trunk/subversion: include/svn_repos.h libsvn_repos/list.c libsvn_repos/repos.c tests/libsvn_repos/repos-test.c

On Sat, Oct 15, 2016 at 5:58 PM, wrote: > Author: stefan2 > Date: Sat Oct 15 15:58:22 2016 > New Revision: 1765088 > > URL: http://svn.apache.org/viewvc?rev=1765088=rev > Log: > Introduce a "directory list" operation at the repos layer. This is the > first step towards an

Re: [SVN-4677] svn up fails after a file is replaced by a directory

On Thu, Apr 6, 2017 at 6:10 AM, Orivej Desh wrote: > I filed a bug at https://issues.apache.org/jira/browse/SVN-4677 > Since the mailing list seems more active, I copy it here. > > * * * > > svn up fails after a file is added, moved, deleted, replaced by a > directory, and a file

Re: 1.10.0-alpha2 is up for signing

On Mon, Mar 6, 2017 at 12:39 PM, Branko Čibej wrote: > On 06.03.2017 12:27, Stefan Fuhrmann wrote: >> On 06.03.2017 10:38, Stefan Sperling wrote: >>> On Tue, Feb 21, 2017 at 01:54:15PM +0100, Stefan Sperling wrote: The new 1.10.1-alpha2 release is up for signing.

Re: [PATCH] Add LZ4 version info to svn --version -v

On Sun, Aug 13, 2017 at 6:53 AM, Ivan Zhakov wrote: > On 11 August 2017 at 23:28, Ivan Zhakov wrote: >> Log message: >> [[[ >> Add LZ4 library verison info to svn --version -v. >> >> * subversion/libsvn_subr/sysinfo.c >> (): Include lz4/lz4internal.h or

Re: [RELEASES] Relaxing the release signature requirements

On Sat, Aug 12, 2017 at 7:35 PM, Daniel Shahaf wrote: > There has been some random discussion about relaxing the release > signature requirements. > > Our hard requirements are: > > - One signature [ASF policy] > - Three +1 votes [ASF policy] > > Our current policy is: >

Giving 1.10 alpha more exposure to gather feedback

Can we try to give 1.10 alpha3 a bit more exposure, in order to gather more feedback? I'm thinking of: - A post to users@, explicitly pointing out the TC resolution features and asking for testing / feedback. This should be short and to the point, and IMO should contain a short version of the

Re: Proposal: new fsfs.conf properties

On Wed, Jul 12, 2017 at 12:27 PM, Branko Čibej <br...@apache.org> wrote: > On 12.07.2017 12:24, Johan Corveleyn wrote: >> On Wed, Jul 12, 2017 at 12:09 PM, Branko Čibej <br...@apache.org> wrote: >>> On 11.07.2017 22:50, Stefan Sperling wrote: >>>> On Tue

Re: Proposal: new fsfs.conf properties

On Wed, Jul 12, 2017 at 12:09 PM, Branko Čibej wrote: > On 11.07.2017 22:50, Stefan Sperling wrote: >> On Tue, Jul 11, 2017 at 09:11:58PM +0200, Branko Čibej wrote: >>> Another issue I have with the proposal is the idea to use file suffixes. >>> That's usually the wrong way to

Re: Proposal: new fsfs.conf properties

On Fri, Jul 14, 2017 at 4:31 PM, Evgeny Kotkov <evgeny.kot...@visualsvn.com> wrote: > Johan Corveleyn <jcor...@gmail.com> writes: > >> Nice! >> >> But how about deltification? Has anyone tried / benchmarked the effect >> of turning off deltification (wi

Re: [RFC] Shelving and Checkpointing

On Mon, Jul 10, 2017 at 2:59 PM, Julian Foad wrote: > Dear Subversion Developers, > > I am delighted to announce that I am working with Assembla to develop > shelving and checkpointing functionality in Subversion. These have > been on the wish list for many years, and are

Re: Proposal: new fsfs.conf properties

On Thu, Jul 13, 2017 at 8:27 AM, Branko Čibej wrote: > On 13.07.2017 04:07, Paul Hammant wrote: >> I flipped _back_ to Python's requests.put(..) in my solution - from a >> regular Svn client. That relies on 'autoversioning=on' for it to work >> over DAV, I mean. In that

Re: Proposal: new fsfs.conf properties

On Fri, Jul 14, 2017 at 1:18 PM, Evgeny Kotkov wrote: > Paul Hammant writes: > >> 1. compression-exempt-suffixes = mp3,mp4,jpeg >> >> 2. deltification-exempt-suffixes = mp3,mp4,jpeg >> >> Regardless of the setting of 'compression-level', #1 above

Re: Proposal: new fsfs.conf properties

On Thu, Jul 13, 2017 at 12:34 PM, Paul Hammant wrote: >> >> >> Mmm ... interesting proposition. Also huge -1 because it'd be a really >> awesome abstraction leak. :) > > > > Is there any way to implement the (reasonable in my opinion) feature > request, without transgressing on

Re: 1.10.0-alpha3 up for signing/testing

Op 19 jul. 2017 18:00 schreef "Daniel Shahaf" : The 1.10.0-alpha3 release artifacts are now available for testing/signing. Please get the tarballs from https://dist.apache.org/repos/dist/dev/subversion and add your signatures there. Thanks! Hi, Just as an FYI: I'm

Re: Proposal: new fsfs.conf properties

On Wed, Jul 12, 2017 at 10:40 PM, Paul Hammant wrote: > I'd be fine with that too if it is also settable via curl --header > "svn:compression: no" for non-client auto-increment operations. I'm wondering whether you'll still need this. You ended up with curl+autoversioning (at

Re: 1.9.6 up for signing/testing

On Fri, Jun 30, 2017 at 3:05 PM, Daniel Shahaf wrote: > The 1.9.6 release artifacts are now available for testing/signing. > > Please get the tarballs from > https://dist.apache.org/repos/dist/dev/subversion > and add your signatures there. > > I'm aiming to release this

Re: 1.8.18 release available for testing/signing

On Mon, Jul 3, 2017 at 12:55 PM, Stefan Sperling wrote: > The 1.8.18 release can now be tested and signed. > Get it from https://dist.apache.org/repos/dist/dev/subversion > as usual, and add your signatures there. Thanks! Summary --- +1 to release Platform Windows

Re: Expected speed of commit over HTTP?

On Thu, Jul 6, 2017 at 4:10 PM, Philip Martin wrote: > Paul Hammant writes: > >> I'm making each revision with.. >> >> dd if=/dev/zero bs=1M count=500 2>/dev/null > >> path/to/file/under/versionControl.dat >> >> .. which is random enough to

Re: Expected speed of commit over HTTP?

On Fri, Jul 7, 2017 at 8:54 AM, Jacek Materna wrote: > Paul, > > Got back from Ops. We don't have anything "special" setup other than what > already been mentioned. Overall the defining metrics for commit performance > are: ssh vs https, rtt on the network path and

FAQ entries #dumpload and (new) #fix-nonLF-log

I have extended the FAQ entry #dumpload [1], about the dump+load procedure, with some caveats and details on the technique to dump+load a large repository with minimal downtime. This is based on a users@ mail from last year [2] (I had been meaning to convert this into a FAQ since then, but only

Re: Benchmarks for PUT for various fsfs config settings.

On Tue, Aug 1, 2017 at 5:36 AM, Paul Hammant wrote: > Chart: > > http://imgur.com/cKe2l4J > > In Python I made two 128GB random files, then uploaded them alternately six > ties three each to the same endpoint in Svn over DAV. That would be a run. > After wiping the server

Re: [RFC] Using LZ4 compression by default

Op 19 aug. 2017 11:40 schreef "Stefan Sperling" : On Fri, Aug 18, 2017 at 10:58:13PM +0300, Evgeny Kotkov wrote: > With all that in mind, I propose that we do (2). Any objections? I want (2) as well. Thanks for doing this work, and for very clearly and transparently describing

Re: 'svn list --search' feature complete?

On Mon, Aug 21, 2017 at 8:14 PM, Daniel Shahaf wrote: > Julian Foad wrote on Mon, 21 Aug 2017 14:09 +0100: >> Also the search term seems to be required to match the entire path, so I >> need to write "co*" rather than just "co" to match "configure.ac". That >> is

'svn list --search' feature complete? (was: re: conflict resolver status update (roll 1.10.0 alpha 1?)

On Sun, Jan 29, 2017 at 10:35 AM, Stefan Fuhrmann wrote: > On 24.01.2017 12:20, Stefan Sperling wrote: ... >> I would like to get an 1.10.0 alpha1 released in February. Unless I hear >> objections I will start rolling this alpha release from trunk and call a >> vote on it

Re: [RELEASES] Relaxing the release signature requirements

On Wed, Aug 16, 2017 at 10:42 PM, Evgeny Kotkov wrote: > Daniel Shahaf writes: > >> Ping? We seem to have consensus on lowering the bar, but not yet consensus >> on what to. It'd be nice to have finished this by the next release. > >

Re: Giving 1.10 alpha more exposure to gather feedback

On Tue, Aug 15, 2017 at 6:35 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Johan Corveleyn wrote on Tue, 15 Aug 2017 11:57 +0200: >> Can we try to give 1.10 alpha3 a bit more exposure, in order to gather >> more feedback? I'm thinking of: >> >> - A post to

Re: Giving 1.10 alpha more exposure to gather feedback

On Thu, Aug 17, 2017 at 5:21 PM, Jacek Materna wrote: > I mentioned earlier on past thread, and still stand by the statement > that setting up a collaborative space beyond email is key to > attracting, enabling and growing an active beta testing user base who > is committed to

Re: Continue the 1.10 alphas?

On Mon, May 1, 2017 at 10:54 PM, Julian Foad wrote: > Just asking... > > As I understand it, we paused the issuing of 1.10 alpha releases because we > considered that the final 1.10 release will need to address the SHA1 > collision issue otherwise it won't be considered a

Re: beta@ feedback mailing list?

On Thu, May 11, 2017 at 4:03 PM, Jacek Materna <ja...@assembla.com> wrote: > On Thu, May 11, 2017 at 10:14 AM, Stefan Sperling <s...@elego.de> wrote: >> On Thu, May 11, 2017 at 01:04:01AM +0200, Johan Corveleyn wrote: >>> How do other ASF projects do this actua

Re: wildcard authz docs question

On Wed, May 10, 2017 at 11:37 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Wed, May 10, 2017 at 5:40 PM, Doug Robinson > <doug.robin...@wandisco.com> wrote: >> >> Johan: >> >> Sorry for my sporadic replies... bin a bit hectic here. >> >&

Re: svn commit: r1794632 - /subversion/trunk/notes/sha1-advisory.txt

On Wed, May 10, 2017 at 1:44 PM, Bert Huijben wrote: >> -Original Message- >> From: Stefan Sperling [mailto:s...@apache.org] >> Sent: woensdag 10 mei 2017 13:34 >> To: Daniel Shahaf >> Cc: dev@subversion.apache.org; comm...@subversion.apache.org

Re: beta@ feedback mailing list?

On Tue, May 9, 2017 at 3:32 PM, Jacek Materna wrote: > Just observing from afar, in my opinion the root of what you are > trying to achieve here ties more to a lack of 'modern' collaboration. > If we want to engage the community/users more (expand the > IB/participation sphere

Re: stricter text conflicts in 1.10

On Tue, May 9, 2017 at 12:14 PM, Stefan Sperling wrote: > I have seen several instances of proposals in our STATUS file where I > cannot merge without text conflicts because I am using a trunk client. > > I suppose most of us use 1.9.x clients to do such merges, because > otherwise

Re: [PATCH] reject SHA1 collisions (was: Re: Progress on SHA-1 fixes in patch releases?)

On Tue, May 9, 2017 at 6:27 PM, Mark Phippard wrote: > On Tue, May 9, 2017 at 12:08 PM, Stefan Sperling wrote: >> >> On Tue, May 09, 2017 at 03:44:22PM +, Daniel Shahaf wrote: >> > Stefan Sperling wrote on Tue, May 09, 2017 at 15:25:23 +0200: >> > > This

Re: beta@ feedback mailing list?

On Tue, May 9, 2017 at 1:06 PM, Daniel Shahaf wrote: > Andreas Stieger wrote on Tue, May 09, 2017 at 12:55:31 +0200: >> Daniel Shahaf wrote: >> > One of the ideas that came up was to establish a dedicated mailing list >> > for beta / pre-release feedback. The thinking is

Re: Check SHA vs Content (was: RE: svn commit: r1759233 - /subversion/trunk/subversion/libsvn_wc/questions.c)

On Tue, Apr 4, 2017 at 11:33 AM, Stefan Sperling wrote: > On Mon, Feb 20, 2017 at 09:05:25AM +0100, Bert Huijben wrote: >> This code is still in trunk without any of the discussed improvements, so >> this change is currently part of 1.10.0-alpha1. >> >> If we don't implement the

Re: Unbuddied issue workflow (was: [jira] [Closed] (SVN-4681) "svn pget svn:externals -r . -R" dramatically slow)

On Wed, May 17, 2017 at 10:56 AM, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, May 16, 2017 at 17:59:28 +0200: >> On Tue, May 16, 2017 at 03:49:32PM +, Daniel Shahaf wrote: >> > We could probably change the "File an issue" jira workflow to prevent >> > people

Re: stricter text conflicts in 1.10

On Sat, May 13, 2017 at 10:38 PM, Stefan Fuhrmann wrote: > On 09.05.2017 12:14, Stefan Sperling wrote: >> >> I have seen several instances of proposals in our STATUS file where I >> cannot merge without text conflicts because I am using a trunk client. >> >> I suppose most of

ra_serf pristine-downloading-optimisation should use capability negotiation

Bringing this point from irc to dev@, so it doesn't get lost: In the context of the recent SHA1-collision problems, and the viability of ra_serf's pristine-downloading-optimisation (which uses SHA-1), Brane suggested on irc: RA optimization "should" become the result of capability negotiation.

Ideas for ra_serf pristine-downloading-optimisation to overcome SHA1 collisions

Not super-relevant in the short term (since it seems we are going in the direction of always rejecting SHA-1 collisions to enter the repository) but maybe useful in the future if we would ever support sha1 collisions: on irc some ideas were floated for overcoming the SHA1 dependence of ra_serf's

Re: wildcard authz docs question

On Wed, May 10, 2017 at 5:40 PM, Doug Robinson <doug.robin...@wandisco.com> wrote: > > Johan: > > Sorry for my sporadic replies... bin a bit hectic here. > > Reply buried deep below. > > On Fri, May 5, 2017 at 5:09 AM, Johan Corveleyn <jcor...@gmail.com> wrote

Re: Check SHA vs Content (was: RE: svn commit: r1759233 - /subversion/trunk/subversion/libsvn_wc/questions.c)

On Tue, May 9, 2017 at 1:21 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Tue, Apr 4, 2017 at 11:33 AM, Stefan Sperling <s...@elego.de> wrote: >> On Mon, Feb 20, 2017 at 09:05:25AM +0100, Bert Huijben wrote: >>> This code is still in trunk without any of

Re: stricter text conflicts in 1.10

On Tue, May 16, 2017 at 4:03 PM, Bert Huijben wrote: > Feel free to revert my patch until we find a way to limit the consequences. > I expect that we also need to fix a few testcases in separate revisions. OK, done in r1795861 (revert of r1731699) and followup in r1795871 to

Re: Dates for 1.10

On Tue, May 23, 2017 at 2:35 PM, Jacek Materna wrote: > Is there a general GA or BETA timeframe/date on the roadmap for the > 1.10 rls? Trying to understand timeline. I'm afraid there is no clear timing we can give (other committers: feel free to correct me). On our roadmap

Re: beta@ feedback mailing list?

Hi Jacek, Sorry for the late response (as I said, this required some chewing :-). I talked a bit about this on irc with Daniel. See my thoughts below (Daniel, feel free to chime in). On Thu, May 11, 2017 at 4:03 PM, Jacek Materna wrote: > Thinking out loud here ... > > Idea

Re: Continue the 1.10 alphas?

On Tue, May 2, 2017 at 3:21 PM, Jacek Materna wrote: > Great to hear on 1.10 move along. > > On SHA1 I can help if you feel it may move things along in parallel - we > ended up having to use the pre-commit hook for our customer base as per >

Re: Continue the 1.10 alphas?

On Thu, May 4, 2017 at 12:34 PM, Jacek Materna wrote: > Agreed - let me looking in Stefan's mods - I can take a look at the > client-side after that to see if I have a slot in the short-term. Okay. Concerning the working copy: IIUC if "fixing" means "making it possible to

Re: wildcard authz docs question

On Thu, May 4, 2017 at 10:16 AM, Daniel Shahaf wrote: > Doug Robinson wrote on Wed, May 03, 2017 at 15:54:50 -0400: ... >> Not seeing it - at least not yet. In Perl the RE needed to handle >> this would be one of the duals, e.g. "/trunk/iota(|/.*)" - the >> either/or

Re: wildcard authz docs question

On Fri, May 5, 2017 at 12:49 AM, Doug Robinson <doug.robin...@wandisco.com> wrote: > > Johan: > > (sorry for the empty message - dwim failed) > > On Thu, May 4, 2017 at 7:26 AM, Johan Corveleyn <jcor...@gmail.com> wrote: >> >> On Thu, May 4, 2017 at 10:16

Re: Dates for 1.10

On Wed, May 24, 2017 at 7:58 PM, Stefan Sperling <s...@elego.de> wrote: > On Wed, May 24, 2017 at 02:44:24PM +0200, Johan Corveleyn wrote: >> Can we restart rolling releases now? > > Sure! I believe all that's needed is a committer who puts on the release > manager hat a

Re: Supporting multiple WC formats

On Thu, Sep 14, 2017 at 6:01 AM, Branko Čibej wrote: > As you may have noticed, I started implementing support for multiple WC > formats on the better-pristines branch, as a prelude to adding support > for compressed pristines without forcing users to upgrade all their > working

Re: Tip of the day: Cheatsheet for common cmdline client operations

On Mon, Sep 18, 2017 at 6:00 PM, Pavel Lyalyakin <pavel.lyalya...@visualsvn.com> wrote: > Hello, > > On Fri, Sep 15, 2017 at 11:57 PM, Johan Corveleyn <jcor...@gmail.com> wrote: >> On Thu, Sep 14, 2017 at 5:27 PM, Pavel Lyalyakin >> <pavel.lyalya...@visualsvn.co

Re: Sparse checkouts suggestion

On Wed, Sep 13, 2017 at 12:45 PM, Paul Hammant wrote: >> >> >> http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py >> > > Excellent! > > I see you posted a StackOverflow answer on that too, Mark - >

Re: Tip of the day: Cheatsheet for common cmdline client operations

Op 20 sep. 2017 17:28 schreef "Pavel Lyalyakin" < pavel.lyalya...@visualsvn.com>: Hello, On Tue, Sep 19, 2017 at 12:42 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > > On Mon, Sep 18, 2017 at 6:00 PM, Pavel Lyalyakin > <pavel.lyalya...@visualsvn.com> wro

Re: Idea: water...@subversion.apache.org mailing list

On Thu, Sep 14, 2017 at 7:57 PM, Joe Orton <jor...@redhat.com> wrote: > On Mon, Aug 21, 2017 at 03:28:35PM +0200, Johan Corveleyn wrote: >> Maybe one of the downstreamers that happens to read this could chime >> in with their thoughts? Right now we're mostly hypothes

Re: Tip of the day: Cheatsheet for common cmdline client operations

On Thu, Sep 14, 2017 at 5:27 PM, Pavel Lyalyakin wrote: ... > I've spent some time to materialize the Quick Start document that I > think will be helpful for novice SVN users. At the moment, it provides > the most basic guidance which should be enough for "quick

Workflow for editing the subversion website

The recent work on our quick-start.html page by Pavel Lyalyakin prompted some thinking about how to better organize our site editing. Pavel asked about lightweight branching and Daniel suggested to copy site/publish to site/staging and having it served as http://subversion.staging.apache.org/ to

How to manage PR's (was: [GitHub] subversion pull request #6: VC should be 14.1 and not 15.0)

On Tue, Oct 10, 2017 at 8:11 PM, asfgit wrote: > Github user asfgit closed the pull request at: > > https://github.com/apache/subversion/pull/6 > > > --- Anybody knows why asfgit closed the PR? I've clicked on the above hyperlink, and saw some comments made by Julian

Re: Sparse checkouts suggestion

On Thu, Sep 21, 2017 at 12:16 PM, Paul Hammant wrote: >> >> >> 2. Previously I forked a medium-sized Monorepo on Github, and did the the >> complete expand/contract work for it - >> https://github.com/paul-hammant-fork/jooby-monorepo-experiment - in Python. >> > > LOGIBALL's Tim

Re: svn commit: r1807836 - in /subversion/trunk: subversion/include/ subversion/include/private/ subversion/libsvn_repos/ subversion/svnadmin/ subversion/svnrdump/ subversion/tests/cmdline/ subversion

On Sat, Sep 9, 2017 at 12:36 AM, wrote: > Author: kotkov > Date: Fri Sep 8 22:36:38 2017 > New Revision: 1807836 > > URL: http://svn.apache.org/viewvc?rev=1807836=rev > Log: > svnadmin: Introduce the `--normalize-props` option for the load and > load-revprops commands. > >

Re: Tip of the day: Cheatsheet for common cmdline client operations

On Tue, Aug 29, 2017 at 2:15 PM, Pavel Lyalyakin <pavel.lyalya...@visualsvn.com> wrote: > Hello, > > On Fri, Aug 25, 2017 at 2:03 PM, Johan Corveleyn <jcor...@gmail.com> wrote: >> >> [ cc -= svnbook-dev, as I guess this will not become book-material. >> More

Re: Unbuddied issue workflow

On Thu, May 18, 2017 at 9:59 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Wed, May 17, 2017 at 10:56 AM, Daniel Shahaf <d...@daniel.shahaf.name> > wrote: >> Stefan Sperling wrote on Tue, May 16, 2017 at 17:59:28 +0200: >>> On Tue, May 16, 2017 at 03:4

Re: Unbuddied issue workflow

On Wed, Aug 30, 2017 at 11:14 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Thu, May 18, 2017 at 9:59 AM, Johan Corveleyn <jcor...@gmail.com> wrote: >> On Wed, May 17, 2017 at 10:56 AM, Daniel Shahaf <d...@daniel.shahaf.name> >> wrote: >>> Stefan Sp

Re: Unbuddied issue workflow

On Mon, Sep 4, 2017 at 12:58 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Sun, Sep 3, 2017 at 11:33 AM, Stefan <luke1...@posteo.de> wrote: >> On 03/09/2017 11:20, Johan Corveleyn wrote: > ... >>> This appears in red letters (with a mailto link on &quo

Re: [PATCH] Let's rework the Quick Start page (publish/quick-start.html)

On Fri, Sep 22, 2017 at 6:57 PM, Pavel Lyalyakin wrote: > Hello, > > It appears that the current SVN Quick Start page[1] is kind of desolate; there > is a discussion about updating it[2]. I want to volunteer for this task and I > am > attaching a patch. :) > > My

Re: [PATCH] Add missing svn:eol-style=native property to site's text files

On Fri, Sep 22, 2017 at 6:00 PM, Pavel Lyalyakin wrote: > Hello, > > Subj. > > Log Message: > [[[ > * publish/faq.en.html > publish/mail > publish/quick-start.html > README > TODO > > Add missing svn:eol-style=native property. > > Patch by Pavel

Re: [PATCH] Let's rework the Quick Start page (publish/quick-start.html)

On Wed, Sep 27, 2017 at 5:08 PM, Pavel Lyalyakin wrote: > Hello Johan, > > Thank you for taking the time to review this patch. :) > > I think that I addressed most of your comments and suggestions in the > attached patch svn-updated-quick-start-v3.patch.txt. I've

Re: [PATCH] Let's rework the Quick Start page (publish/quick-start.html)

On Tue, Oct 3, 2017 at 11:37 AM, Daniel Shahaf wrote: > Pavel Lyalyakin wrote on Mon, 02 Oct 2017 13:41 +0300: >> I am going to work on further improvements and as soon as they are ready, I >> will >> start a new [PATCH] thread. However, what about creating a lightweight

Re: Idea: water...@subversion.apache.org mailing list

On Mon, Aug 21, 2017 at 1:48 PM, Julian Foad wrote: > Daniel Shahaf wrote: >> Would it be useful to have a mailing list dedicated for communications >> between us (upstream developers) and various downstream packagers and >> distributors? >> >> I suppose this basically

Re: Shelving / Checkpointing thoughts

On Fri, Aug 25, 2017 at 4:59 PM, Julian Foad <julianf...@apache.org> wrote: > Johan Corveleyn wrote: >> On Fri, Aug 25, 2017 at 3:33 PM, Julian Foad <julianf...@apache.org> wrote: > [...]>> The Checkpoint feature could add the copy-and-modify facility > for the

Re: Shelving and Checkpointing support log messages

On Fri, Aug 25, 2017 at 11:08 AM, Julian Foad wrote: > Daniel Shahaf wrote: >> Julian Foad wrote on Thu, 24 Aug 2017 19:46 +0100: >>> One rough edge is that "unshelving" a patch or finishing/squashing a >>> checkpoint series simply discards the log message(s). [...] >> >>

Re: Towards a Shelving MVP

On Mon, Aug 28, 2017 at 9:05 PM, Julian Foad wrote: > Branko Čibej wrote: >> On the topic of storing patches, I'd like to propose an alternative >> implementation. >> >> Instead of saving a set of patches, save two sets of (untranslated >> pristine) files: >> >> * All

<    4   5   6   7   8   9   10   11   12   13   >