On 2024/01/30 6:15, Daniel Sahlberg wrote:
> Good catch! How about:
>
> [[[
> Index: subversion/svnserve/svnserve.c
> ===
> --- subversion/svnserve/svnserve.c (revision 1915424)
> +++ subversion/svnserve/svnserve.c (working
Den mån 22 jan. 2024 kl 04:05 skrev Branko Čibej :
> On 13.01.2024 09:58, Daniel Sahlberg wrote:
>
> Since there wasn't any replies to this and I think the code was working
> fine in all my tests, I comitted as r1915214. Although I finally decided to
> solve the spurious revert messages in a
Den mån 29 jan. 2024 kl 13:50 skrev Jun Omae :
> On 2023/03/20 10:27, phi...@apache.org wrote:
> > Author: philip
> > Date: Mon Mar 20 01:27:41 2023
> > New Revision: 1908547
> >
> > URL: http://svn.apache.org/viewvc?rev=1908547=rev
> > Log:
> > Add SIGTERM/SIGINT handling to svnserve, this
Den mån 29 jan. 2024 kl 13:26 skrev Jun Omae :
> On 2024/01/13 18:16, dsahlb...@apache.org wrote:
> > Author: dsahlberg
> > Date: Sat Jan 13 09:16:26 2024
> > New Revision: 1915215
> >
> > URL: http://svn.apache.org/viewvc?rev=1915215=rev
> > Log:
> > Manage spurious Reverted message caused by
On 2023/03/20 10:27, phi...@apache.org wrote:
> Author: philip
> Date: Mon Mar 20 01:27:41 2023
> New Revision: 1908547
>
> URL: http://svn.apache.org/viewvc?rev=1908547=rev
> Log:
> Add SIGTERM/SIGINT handling to svnserve, this allows it to exit more
> gracefully which allows tools like valgrind
On 2024/01/13 18:16, dsahlb...@apache.org wrote:
> Author: dsahlberg
> Date: Sat Jan 13 09:16:26 2024
> New Revision: 1915215
>
> URL: http://svn.apache.org/viewvc?rev=1915215=rev
> Log:
> Manage spurious Reverted message caused by non-W access to files
> owned by another user. Part of Issue
6 matches
Mail list logo