On Sat, Jul 11, 2020 at 8:26 PM sebb wrote:
>
> On Sat, 11 Jul 2020 at 20:57, Craig Russell wrote:
> >
> > Testing the (move to emeritus) and (move to active) with the one emeritus
> > request we have:
> >
> > Move to emeritus: No errors reported. The file was not moved from
> > emeritus-reques
On Sat, 11 Jul 2020 at 20:57, Craig Russell wrote:
>
> Testing the (move to emeritus) and (move to active) with the one emeritus
> request we have:
>
> Move to emeritus: No errors reported. The file was not moved from
> emeritus-requests-received to emeritus. The entry in members.txt was moved t
Testing the (move to emeritus) and (move to active) with the one emeritus
request we have:
Move to emeritus: No errors reported. The file was not moved from
emeritus-requests-received to emeritus. The entry in members.txt was moved to
the wrong place. The active member count was not adjusted.
Hi Sebb,
Does this mean that multiUpdate will now work with multiple directory roots, or
is there still an update needed for svnmucc in svn.rb?
Thanks,
Craig
> On Jul 11, 2020, at 6:59 AM, sebb wrote:
>
> On Sat, 11 Jul 2020 at 08:56, Greg Stein wrote:
>>
>> On 2020/07/10 15:05:05, sebb wr
On Sat, 11 Jul 2020 at 08:56, Greg Stein wrote:
>
> On 2020/07/10 15:05:05, sebb wrote:
> >...
> > Of course this will only be needed if the permission issue is not sorted.
>
> With the help of Humbedooh, I believe we have sorted out the permissions. I
> was able to do this via svnmucc, but that
On 2020/07/10 15:05:05, sebb wrote:
>...
> Of course this will only be needed if the permission issue is not sorted.
With the help of Humbedooh, I believe we have sorted out the permissions. I
was able to do this via svnmucc, but that was because of elevated
permissions. A Member with access to t
