On Fri, Nov 3, 2023 at 8:15 AM Daniel Sahlberg
wrote:
>
> Hi,
>
> I don't know about the policy for deleting unmaintained / no longer relevant
> code, so I'm asking here first.
>
> /tools/dev/iz/
> (https://svn.apache.org/repos/asf/subversion/trunk/tools/dev/iz/) seems to be
> a tool to
On Fri, Nov 3, 2023 at 6:45 AM Daniel Sahlberg
wrote:
>
> Den fre 3 nov. 2023 kl 10:00 skrev Stefan Sperling :
>>
>> On Fri, Nov 03, 2023 at 12:00:32AM -0400, Nathan Hartman wrote:
>
> [...]
>>
>> >
>> >
>> > Hi all,
>> >
>> > Previously I mentioned I plan to RM for the upcoming 1.14.3 release.
On Sat, Apr 22, 2023 at 4:30 AM Branko Čibej wrote:
>
> On 22.04.2023 10:27, Branko Čibej wrote:
>
> On 21.04.2023 16:43, Johan Corveleyn wrote:
>
>
> My plan is to revert r1845377 during next weekend. For the first bulletpoint
> nothing has to be done, but if consensus changes during the week,
On Mon, Nov 21, 2022 at 5:47 AM Daniel Sahlberg
wrote:
>
> Hi,
>
> On the Binary Packages page [1], under Windows, there is a link to SlikSVN:
> "...maintained by Bert Huijben, SharpSvn project".
>
> The name and project links to open.collab.net, which currently doesn't work
> (outdated SSL
On Mon, Apr 11, 2022 at 6:14 PM Evgeny Kotkov
wrote:
>
> svn-role writes:
>
> > Merge r1883355 from trunk:
> >
> > * r1883355
> >Use the APR-1.4+ API for flushing file contents to disk.
> >Justification:
> > Reduce code duplication between APR and SVN.
> >Votes:
> > +1:
On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf wrote:
>
> Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > daniel.l.sahlb...@gmail.com>:
> >
> > > This commit doesn't look correct.
> > >
> > > I executed the
On Sun, Apr 10, 2022 at 4:37 PM Branko Čibej wrote:
>
> On 10.04.2022 22:26, Branko Čibej wrote:
> > On 10.04.2022 22:02, Mark Phippard wrote:
> >> On Sun, Apr 10, 2022 at 3:27 PM Daniel Shahaf
> >> wrote:
> >>> Mark Phippard wrote on Sun, A
On Sun, Apr 10, 2022 at 3:27 PM Daniel Shahaf wrote:
>
> Mark Phippard wrote on Sun, Apr 10, 2022 at 15:16:58 -0400:
> > So I was wondering how, using the gpg command. I can get the other
> > elements we include .. such as: Stefan Sperling
> > [2048R/4F7DBAA99A59B97
On Sun, Apr 10, 2022 at 2:22 PM Daniel Shahaf wrote:
>
> Mark Phippard wrote on Sun, 10 Apr 2022 16:30 +00:00:
> > Looking at past release announcements, they include a section on who
> > signed the release that looks like this:
> >
> >Stefan Sperling [2048R/4F7D
Looking at past release announcements, they include a section on who
signed the release that looks like this:
Stefan Sperling [2048R/4F7DBAA99A59B973] with fingerprint:
8BC4 DAE0 C5A4 D65F 4044 0107 4F7D BAA9 9A59 B973
Branko Čibej [4096R/1BCA6586A347943F] with fingerprint:
BA3C
On Thu, Apr 7, 2022 at 10:07 AM Nathan Hartman wrote:
>
> On Thu, Apr 7, 2022 at 9:49 AM Stefan Sperling wrote:
>>
>> On Thu, Apr 07, 2022 at 09:37:08AM -0400, Mark Phippard wrote:
>> > Just a reminder, the 1.10.8 and 1.14.2 releases are posted and
>> >
Just a reminder, the 1.10.8 and 1.14.2 releases are posted and
available for testing and signatures. Please try to get them completed
by this Sunday.
The plan is to make the release available on Tuesday April 12.
Thanks
Mark
On Tue, Apr 5, 2022 at 4:49 PM Johan Corveleyn wrote:
>
> Thanks all for sharing your gpg key hurdles. It saved me a lot of time
> when I ran into the same issues while verifying Mark's signature :-).
>
> 1. Signature algorithm not recognized
> -> updated my gpg to latest version (2.3.4)
When I
On Mon, Apr 4, 2022 at 3:49 AM Daniel Sahlberg
wrote:
>
> Den sön 3 apr. 2022 kl 20:46 skrev Mark Phippard :
>>
>> On Sun, Apr 3, 2022 at 2:43 PM Daniel Sahlberg
>> wrote:
>> >
>> > Den sön 3 apr. 2022 kl 19:55 skrev Mark Phippard :
>> >>
On Sun, Apr 3, 2022 at 2:43 PM Daniel Sahlberg
wrote:
>
> Den sön 3 apr. 2022 kl 19:55 skrev Mark Phippard :
>>
>> On Sun, Apr 3, 2022 at 1:40 PM Daniel Sahlberg
>> wrote:
>>
>> > It seems to be a problem mostly related to my key. I can't get the
>>
On Sun, Apr 3, 2022 at 1:40 PM Daniel Sahlberg
wrote:
> It seems to be a problem mostly related to my key. I can't get the committer
> signature list [1] to include my key (and thus the script doesn't download it
> to the KEYS file).
FWIW, I think you can sign the release even if you are not
On Sun, Apr 3, 2022 at 11:40 AM Daniel Sahlberg
wrote:
>
> Den lör 2 apr. 2022 kl 15:27 skrev Mark Phippard :
>>
>> The 1.10.8 release artifacts are now available for testing/signing.
>>
>> Please get the tarballs from
>> https://dist.apache.org/repos
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
and
gpg --list-keys
/Users/markphip/.gnupg/pubring.kbx
--
pub ed25519 2022-03-21 [SC]
EC25FCC105618D04ADB43429C4416167349A3BCB
uid [ultimate] Mark Phippard
Mark
I've not done much to the website in years and want to understand the
current process.
I believe all changes should be made to staging and then merged to publish?
I am OK with this but it seems mildly difficult to manage the merges
with concurrent development that is happening. Is there any
On Sat, Apr 2, 2022 at 1:52 PM Yasuhito FUTATSUKI
wrote:
>
> On 2022/04/02 22:39, Mark Phippard wrote:
> > The releases are posted for signing. The process all went well except
> > for one part. When I ran the script to create the tag it fails with
> > this error:
> &
On Sat, Apr 2, 2022 at 9:39 AM Mark Phippard wrote:
>
> The releases are posted for signing. The process all went well except
> for one part. When I ran the script to create the tag it fails with
> this error:
>
> INFO:root:Creating tag for 1.14.2
> INFO:root:Bumping version
The releases are posted for signing. The process all went well except
for one part. When I ran the script to create the tag it fails with
this error:
INFO:root:Creating tag for 1.14.2
INFO:root:Bumping version numbers on the branch
Traceback (most recent call last):
File
The 1.14.2 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!
The 1.10.8 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!
I think we are all set for tomorrow. I updated CHANGES on trunk for
both releases and backported to the branches. Feel free to review and
make edits if you see fit. I will just go with whatever is on the
branches tomorrow AM.
Now, back to $DAYJOB
Mark
On Fri, Apr 1, 2022 at 6:50 AM Mark Phippard wrote:
> I was able to run the script without problem, so I think I am all set.
> The release.py script will still fail when it tries to download the
> KEYS but I am assuming that is the last step it does in that part of
> the process. Pre
I will do a dry-run this AM and run all the tests to confirm but I
believe we are all set to produce the release tarballs tomorrow.
I might do the commits to CHANGES later today as I see no harm in
doing it ahead of time. This will also give a window where people can
make edits if they see fit.
;
> On Thu, Mar 31, 2022 at 7:48 PM Daniel Shahaf wrote:
> >
> > Mark Phippard wrote on Wed, Mar 30, 2022 at 08:01:32 -0400:
> > > I am still a little unsure what to do about the KEYS file when we
> > > produce this release.
>
> Okay, so https://downloads.apac
On Thu, Mar 31, 2022 at 2:49 PM Nathan Hartman wrote:
> There's nothing that says we have to merge everything in STATUS right
> now. If we get the votes approving the remaining items, that's great,
> but if not, then it may get into the next release cycle.
I agree. I also do not have to roll the
We are getting closer to Saturday when I intended to roll the releases.
There are a couple of impediments that may need to delay the release.
Looking for feedback:
1. I posted about the PGP KEYS file. Looking for guidance on how to
proceed. I think manually sending me a file to use could be an
Could someone perhaps manually merge this?
We need the backports working to finish this process and get the release out.
On Thu, Mar 31, 2022 at 2:31 AM Daniel Sahlberg
wrote:
>
> Hi,
>
> The backport below is stuck. backport.pl reports:
>
> [[[
> Warning summary
> ===
>
>
On Wed, Mar 30, 2022 at 9:02 AM Julian Foad wrote:
>
> Karl Fogel wrote:
> > I think printing these messages to stderr makes the most sense.
> > There are plenty of programs out there that parse the stdout of
> > 'svn'; we don't want to interfere with them.
> >
> > As you point out, it's
I am still a little unsure what to do about the KEYS file when we
produce this release.
Our release.py script no longer works for whatever it used to do and
throws an error. I do not know if more errors will happen when I get
to the steps of publishing the release to /dist later on.
I just
I intend to produce the tarballs for the 1.10.8 and 1.14.2 this
Saturday (April 2). I will send out the call for signatures sometime
in the AM US Eastern time.
We will aim for a release date of Tuesday (April 12), which will give
everyone until Sunday (April 10) to get their votes and signatures
If anyone is interested in looking at what I have been doing to run
the SVN RM process I am keeping it all here:
https://github.com/markphip/svnrm
In summary, I am using Docker to build an image for running the
release.py script. It can also run the build process but I am no
longer doing that in
What is this file used for? Is it displayed on the website somewhere?
It is just showing merged changes since the last release? So I guess
could help us write CHANGES?
Mark
On Mon, Mar 28, 2022 at 4:01 PM Daniel Sahlberg
wrote:
>
> Once again I've executed this manually to make sure it
Uggh ... so in looking at 1.10.x it occurred to me you need to merge
the branch specified.
Nevermind, will remove the veto and put it back
Mark
On Mon, Mar 28, 2022 at 10:31 AM Mark Phippard wrote:
>
> Just an fyi ..
>
> I went through STATUS and merged most of the items to
Just an fyi ..
I went through STATUS and merged most of the items to a 1.14.x WC and
then ran all tests. They all run, which is great.
However, r1899227 does not merge clean. I had to manually resolve
conflicts. So that needs to be addressed so we can backport it?
Stefan, if you just want to
I intend to start the release process for SVN 1.10.x and 1.14.x in the
near future. It would be great if we could get the STATUS files
cleaned out so we can include as many fixes as possible in these
releases. It has been a long time since we did a release so we may as
well make it count.
I am
On Sun, Mar 27, 2022 at 5:47 PM Daniel Sahlberg
wrote:
>
> Den sön 27 mars 2022 kl 22:18 skrev Mark Phippard :
>>
>> This backport broke this script for me:
>>
>> https://svn.apache.org/viewvc?view=revision=1899256
>>
>> davautocheck.sh: Adding groups
This backport broke this script for me:
https://svn.apache.org/viewvc?view=revision=1899256
davautocheck.sh: Adding groups for mod_authz_svn tests
AH00526: Syntax error on line 161 of
/home/markphip/subversion-1.14.2/subversion/tests/cmdline/httpd-20220327-200833/cfg:
AuthzSVNAccessFile and
On Sun, Mar 27, 2022 at 3:35 PM Daniel Sahlberg
wrote:
>
> Den sön 27 mars 2022 kl 13:05 skrev Mark Phippard :
>>
>> On Sun, Mar 27, 2022 at 7:00 AM Daniel Sahlberg
>> wrote:
>> >
>> > Hi,
>> > It is due to the migration of svn-qavm to the
On Sun, Mar 27, 2022 at 1:45 PM Daniel Sahlberg
wrote:
>
> Den sön 27 mars 2022 kl 19:33 skrev Daniel Shahaf :
>>
>> It's not mutually exclusive; someone can run the script locally. I'd
>> recommend
>> to run merge-approved-backport.py without arguments.
>
>
> Fails for me:
> [[[
> $
On Sun, Mar 27, 2022 at 9:53 AM Nathan Hartman wrote:
>
> On Sun, Mar 27, 2022 at 9:46 AM Stefan Sperling wrote:
>>
>> On Sun, Mar 27, 2022 at 09:35:51AM -0400, Nathan Hartman wrote:
>> > On Sun, Mar 27, 2022 at 9:05 AM Mark Phippard wrote:
>> > >
>&g
On Sun, Mar 27, 2022 at 8:50 AM Nathan Hartman wrote:
>
> On Sun, Mar 27, 2022 at 7:05 AM Mark Phippard wrote:
>>
>> On Sun, Mar 27, 2022 at 7:00 AM Daniel Sahlberg
>> wrote:
>> >
>> > Hi,
>> > It is due to the migration of svn-qavm to the
On Sun, Mar 27, 2022 at 7:00 AM Daniel Sahlberg
wrote:
>
> Hi,
> It is due to the migration of svn-qavm to the new host as requested by ASF
> Infra. I'll look into it right away, it has been on my todo list since last
> week, sorry!
> /Daniel
Thanks. We will want it to get this release process
Is the automated backports script no longer running? I notice the
Approved changes have not been merged.
Is that something we can get running again?
Thanks
Mark
.
Votes:
+1: futatuki, stsp
On Thu, Mar 24, 2022 at 8:24 PM Mark Phippard wrote:
>
> I am inching closer to taking on the RM duties so it would be good if
> people started to clean up the STATUS file and get things merged.
>
> Looking at what is in there ... these items all seem B
I am inching closer to taking on the RM duties so it would be good if
people started to clean up the STATUS file and get things merged.
Looking at what is in there ... these items all seem Bindings related
so don't they just need the 2 votes? Did someone just forget to move
them to the Approved
On Wed, Mar 23, 2022 at 5:51 PM Julian Foad wrote:
> I thought maybe we would like to show this detail by default, and
> suppress it when '--quiet' is passed. (Not implemented in this demo patch.)
>
> I was also mildly surprised to see that the fetches are not necessarily
> all grouped together
On Tue, Mar 22, 2022 at 11:51 PM Daniel Shahaf wrote:
>
> Mark Phippard wrote on Mon, Mar 21, 2022 at 16:46:55 -0400:
> > On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote:
> > > On Mon, Mar 21, 2022 at 12:44:44PM -0400, Mark Phippard wrote:
> > > >
On Tue, Mar 22, 2022 at 2:10 PM Mark Phippard wrote:
>
> On Tue, Mar 22, 2022 at 2:01 PM Mark Phippard wrote:
> >
> > On Tue, Mar 22, 2022 at 1:47 PM Daniel Sahlberg
> > wrote:
> > >
> > > Den tis 22 mars 2022 kl 18:09 skrev Mark Phippard :
> >
On Tue, Mar 22, 2022 at 2:01 PM Mark Phippard wrote:
>
> On Tue, Mar 22, 2022 at 1:47 PM Daniel Sahlberg
> wrote:
> >
> > Den tis 22 mars 2022 kl 18:09 skrev Mark Phippard :
> >>
> >> Using 1.14.1, I have confirmed I can build and run the tests for all
&g
On Tue, Mar 22, 2022 at 1:47 PM Daniel Sahlberg
wrote:
>
> Den tis 22 mars 2022 kl 18:09 skrev Mark Phippard :
>>
>> Using 1.14.1, I have confirmed I can build and run the tests for all
>> bindings. Only thing left is the DAV tests and figuring out how to
>> setup
On Tue, Mar 22, 2022 at 1:05 PM Yasuhito FUTATSUKI
wrote:
>
> Hi,
>
> On 2022/03/23 1:54, Mark Phippard wrote:
> > On Tue, Mar 22, 2022 at 10:10 AM Mark Phippard wrote:
> >>
> >> On Tue, Mar 22, 2022 at 10:03 AM Mark Phippard wrote:
> >>> This
On Tue, Mar 22, 2022 at 10:10 AM Mark Phippard wrote:
>
> On Tue, Mar 22, 2022 at 10:03 AM Mark Phippard wrote:
> > This all mostly works. Exception is Python. It sounds like I need to
> > take steps to regenerate the Python bindings for Python 2. The
> > question is how.
On Tue, Mar 22, 2022 at 10:03 AM Mark Phippard wrote:
> This all mostly works. Exception is Python. It sounds like I need to
> take steps to regenerate the Python bindings for Python 2. The
> question is how. So far I have been told I need to re-run autogen.sh.
> I did so. I then ran
On Tue, Mar 22, 2022 at 12:38 AM Nathan Hartman
wrote:
>
> On Mon, Mar 21, 2022 at 9:18 PM Jun Omae wrote:
> >
> > On Tue, Mar 22, 2022 at 9:10 AM Mark Phippard wrote:
> > >
> > > This seems to be the main thing I am stuck on. I used Debian Buster so
&g
> On Mar 21, 2022, at 8:10 PM, Mark Phippard wrote:
>
> On Mon, Mar 21, 2022 at 4:59 PM Stefan Sperling wrote:
>>
>>> On Mon, Mar 21, 2022 at 04:46:55PM -0400, Mark Phippard wrote:
>>> On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote:
>>&
On Mon, Mar 21, 2022 at 4:59 PM Stefan Sperling wrote:
>
> On Mon, Mar 21, 2022 at 04:46:55PM -0400, Mark Phippard wrote:
> > On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote:
> > > This might be a swig problem? Perhaps the version of swig and the
> > > ver
On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote:
>
> On Mon, Mar 21, 2022 at 12:44:44PM -0400, Mark Phippard wrote:
> > I have been toying with the idea of volunteering to be Release
> > Manager. I am not ready to do so yet as I have run into numerous
> > pr
I have been toying with the idea of volunteering to be Release
Manager. I am not ready to do so yet as I have run into numerous
problems.
The docs are decent but they are definitely written to an audience
that knows a lot of things that I do not and it feels like a lot of
knowledge is just
On Mon, Mar 14, 2022 at 6:48 AM Julian Foad wrote:
>
> Dear dev community, and especially Karl and Mark:
>
> A plea to test the current design/implementation.
>
> I wonder if we are missing some perspective.
Hi Julian,
I do not believe I can offer much in the way of testing, but I do want
to
On Sun, Mar 13, 2022 at 3:32 AM Johan Corveleyn wrote:
>
> On Fri, Mar 11, 2022 at 9:17 PM Nathan Hartman
> wrote:
> > If possible and not overly burdensome, I think it would be a good
> > thing to keep the "restore" functionality for the following reasons:
> [snip]
>
> I agree. I know about
On Fri, Mar 11, 2022 at 12:21 PM Julian Foad wrote:
> > This is where the question comes in ... why does not having the
> > pristines change this? The WC still knows what files it has and what
> > revisions. Isn't this what drives the process? I just do not
> > understand what has changed that
On Fri, Mar 11, 2022 at 10:24 AM Evgeny Kotkov
wrote:
>
> Julian Foad writes:
>
> > Conclusions:
> >
> >
> > It is certainly possible that we could modify "update" and the other
> > "online" operations, at least, and the previously "offline" operations
> > too if we want, to make
On Fri, Mar 11, 2022 at 5:16 AM Daniel Sahlberg
wrote:
>
> Den fre 11 mars 2022 kl 11:04 skrev Julian Foad :
>>
>> Daniel Sahlberg wrote:
>> > I'm taking an opposite position with regards on where this should be
>> > administred. [...] I would prefer a multi-level approach where the
>> >
On Sun, Mar 6, 2022 at 11:19 PM Karl Fogel wrote:
[snipped]
Agree with everything you have said.
> I do understand the reasons why Evgeny thought pre-fetching
> pristines for modified files as part of an 'update' could be a
> good idea.
My recollection of the first version of this patch,
On Fri, Mar 4, 2022 at 3:52 PM Julian Foad wrote:
>
> > Mark Phippard wrote:
> >> [...] For an update, I think it is unexpected and undesirable. [...]
>
> I had a talk with Karl about this, and now I understand the concern much
> better.
>
> (Karl, please correct
On Tue, Mar 1, 2022 at 10:34 AM Julian Foad wrote:
>
> On Feb 18 2022, Mark Phippard wrote:
> >> [It fetches and stores pristines of modified files;] it doesn't mean
> >> "store no pristines" in that WC.
> >
> > I am curious what Karl thinks g
On Sat, Feb 19, 2022 at 10:39 AM Stefan Kueng wrote:
> > This use-case is already supported by the use of the oldest WC format by
> > default, isn't it?
>
> ah, yes. If the oldest supported format is used then of course the env
> variable isn't necessary. I was under the impression that the
On Fri, Feb 18, 2022 at 3:21 PM Julian Foad wrote:
>
> Karl Fogel wrote:
> > Is the above happening in MVP?
>
> Yes. I was describing what Evgeny created last year in the
> 'pristines-on-demand' branch.
>
> > I ask because my understanding of
> > MVP was that it's not doing this opportunistic
On Thu, Feb 17, 2022 at 5:52 PM Julian Foad wrote:
>
> Mark Phippard wrote:
> >> | update/switch | Always | Always + Hydrate |
> >
> >Can you expand on this one a bit? I presume what you mean is if you
> >have local mods to a file and run update/switch and there i
On Thu, Feb 17, 2022 at 5:09 PM Julian Foad wrote:
>
> Awesome, Nathan!
I agree.
> | update/switch | Always | Always + Hydrate |
Can you expand on this one a bit? I presume what you mean is if you
have local mods to a file and run update/switch and there is a newer
revision of the file in the
On Thu, Feb 17, 2022 at 9:41 AM Julian Foad wrote:
>
> Mark Phippard wrote:
> [...]
> >currently there is no pristine. Now I run svn diff and I see the
> >result. The command ends ... there is still no pristine. [...] If, when the
> >command finishes, there are
On Wed, Feb 16, 2022 at 9:07 AM Mark Phippard wrote:
> > FWIW, I just assumed that this *isn't* the intended entry point to
> > the feature. That is, it's just how things happen to be on the
> > branch right now, but (presumably) Julian isn't saying that he
> > thinks
On Wed, Feb 16, 2022 at 9:59 AM Julian Foad wrote:
>
> Mark Phippard wrote:
> >> "The core idea is that we start to maintain the following invariant: only
> >> the modified files have their pristine text-base files available on the
> >> disk."
> &
On Wed, Feb 16, 2022 at 2:53 AM Karl Fogel wrote:
> >Are you saying this is how you would activate this no-pristines
> >feature? If so, that sounds like a poor UX. As a user, I would
> >not
> >expect the version number to be connected to a feature like that
> >Or
> >more accurately, I could
On Wed, Feb 16, 2022 at 4:16 AM Julian Foad wrote:
> "The core idea is that we start to maintain the following invariant: only the
> modified files have their pristine text-base files available on the disk."
>
On Tue, Feb 15, 2022 at 12:00 PM Julian Foad wrote:
>
> Karl Fogel wrote:
> > [...] there has to be some way for the user to specify at checkout
> > time [...]
>
> Currently: "svn checkout --compatible-version=1.15". No feature name
> involved. Not saying that's good, just that's the current
On Sat, Feb 12, 2022 at 3:15 PM Karl Fogel wrote:
> The name of the "pristines-on-demand" branch implies a certain
> behavior -- namely, that pristines can, via some UI, be fetched on
> demand :-). But in the MVP we're talking about, pristines in a
> given WC are either all present or all
On Thu, Feb 10, 2022 at 7:25 AM Julian Foad wrote:
>
> It strikes me now, given Subversion's "mature, stable" phase of life,
> that we should default to backward compatibility.
>
> Change the default to --compatible-version=1.8 (same as =1.14), instead
> of 1.15 (format 32). Both for "checkout"
On Wed, Feb 9, 2022 at 7:51 AM Stefan Sperling wrote:
>
> On Wed, Feb 09, 2022 at 07:23:55AM -0500, Mark Phippard wrote:
> > 2. We need a RM to produce the release. Only a handful of people have
> > done this and I am not one of them so I cannot comment on how hard
> > th
On Wed, Feb 9, 2022 at 7:32 AM Julian Foad wrote:
>
> Mark Phippard wrote:
> > [...] Or are you suggesting
> > the vote in STATUS essentially "counts" as the approval we need?
>
> That, plus automating the mechanical parts, forms the essence of it.
> These
I am top-posting because the comments are just general feedback.
I think any changes that help create releases would not be a bad
thing. If we were to adopt a process like this though, I do think we
should be a bit selective about the type of bug that warrants a
release like this. Releases, even
On Mon, Jan 24, 2022 at 10:44 AM Daniel Shahaf wrote:
> > > >I return to my "two camps" argument. The people that do not want
> > > >plaintext passwords to be cached ... do not want them being
> > > >cached.
> > >
> > > I see what you mean.
> > >
> > > If svn is compiled to not cache passwords,
On Fri, Jan 21, 2022 at 7:22 PM Karl Fogel wrote:
>
> On 21 Jan 2022, Mark Phippard wrote:
> >One aspect of the previous thread that came up is that someone
> >demonstrated a simple script to create a cached password (as a
> >workaround for current users). That
On Fri, Jan 21, 2022 at 6:39 PM Karl Fogel wrote:
> >2) If we have to add a new compile option, then I suggest we go
> >all
> >the way and also close the backdoor that exists. IOW, if svn is
> >compiled without plaintext support then it also should not be
> >able to
> >read an existing stored
On Thu, Jan 20, 2022 at 11:50 PM Karl Fogel wrote:
>
> On 20 Jan 2022, Mark Phippard wrote:
> >I have made the suggestion before and I want to say there was
> >agreement from anyone that responded. So if nothing else anyone
> >that
> >objects to this is not speak
On Thu, Jan 20, 2022 at 4:06 PM Karl Fogel wrote:
> So: shall we just go back to the old way, but with a compile-time option
> to remove support for it?
I have made the suggestion before and I want to say there was
agreement from anyone that responded. So if nothing else anyone that
objects to
On Thu, Jan 20, 2022 at 1:01 PM Daniel Sahlberg
wrote:
>
> Den tors 20 jan. 2022 kl 14:57 skrev Mark Phippard :
>>
>> I was in the process of replying to Karl's email and why I do not
>> think his approach is the way to go when I had the following idea.
>>
>> W
On Wed, Jan 19, 2022 at 9:08 PM Karl Fogel wrote:
>
> This thread has been dormant for a while, but the question hasn't
> gone away. It would be great if we could reach a consensus. Here
> is a combined proposal (based on proposals quoted below from
> Daniel Sahlberg and Stefan Sperling):
>
>
I was in the process of replying to Karl's email and why I do not
think his approach is the way to go when I had the following idea.
What if we add a new password storage module in the spirit of the
gnome-keyring, gpg modules that stores the password in some kind of
obfuscated format in the auth
On Wed, Dec 15, 2021 at 4:59 PM Pavel Lyalyakin
wrote:
>
> It seems that the list markup is wrong. There should be (unordered list)
> tag instead of (paragraph).
>
> I also think that it makes sense to include links to the SVN Edge's page[1]
> and the announcement made by VisualSVN Team[2].
g4j problem. Should we write a new item about
>> this for the web site? Several people (Pavel Lyalyakin, Mark Phippard) has
>> made valuable comments and I can (with their permission) distil some
>> condensed reply.
>>
>> Kind regards,
>> Daniel
>
>
> There is o
On Wed, Dec 15, 2021 at 6:13 AM Daniel Sahlberg
wrote:
>
> Hi,
>
> There has been several different requests regarding if Subversion is
> vulnerable to the latest log4j problem. Should we write a new item about this
> for the web site? Several people (Pavel Lyalyakin, Mark
Thanks for taking the time to summarize the thread as well as the
additional research you added.
On Sun, Oct 3, 2021 at 6:39 AM Daniel Sahlberg
wrote:
> The decision to change the compile time default was made in 2018-10-31 within
> less than 12 hours and without much debate. It was committed
On Mon, Aug 30, 2021 at 3:17 AM Lorenz wrote:
>
> Evgeny Kotkov wrote:
>
> >Karl Fogel writes:
> >
> >> 1) Make pristine text-base files optional. See issue #525 for
> >> details. In summary: currently, every large file uses twice the
> >> storage on the client side, and yet for most of these
On Sun, Aug 29, 2021 at 9:04 AM Branko Čibej wrote:
>
> On 29.08.2021 14:21, Mark Phippard wrote:
> > On Sun, Aug 29, 2021 at 8:12 AM Branko Čibej wrote:
> >> On 27.08.2021 15:55, Evgeny Kotkov wrote:
> >>
> >>>1. Complete the work o
On Sun, Aug 29, 2021 at 8:12 AM Branko Čibej wrote:
>
> On 27.08.2021 15:55, Evgeny Kotkov wrote:
>
> > 1. Complete the work on ^/subversion/branches/multi-wc-format so that the
> > client would work with both the new and old working copy formats, for
> > a seamless user experience
1 - 100 of 828 matches
Mail list logo
