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 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
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 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
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 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 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 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 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
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, 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):
>
>
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 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 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
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 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
>> >
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.
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 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 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
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 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 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,
801 - 828 of 828 matches
Mail list logo
