Re: Emeritus svn operations in roster/workbench

On Tue, 2 Jun 2020 at 01:45, Craig Russell wrote: > > > > > On Jun 1, 2020, at 4:52 PM, sebb wrote: > > > > On Mon, 1 Jun 2020 at 23:30, Craig Russell > > wrote: > >> > >> > >> > >>> On Jun 1, 2020, at 3:17 PM, sebb >>> > wrote: > >>> > >>>

Re: Emeritus svn operations in roster/workbench

> On Jun 1, 2020, at 4:52 PM, sebb wrote: > > On Mon, 1 Jun 2020 at 23:30, Craig Russell > wrote: >> >> >> >>> On Jun 1, 2020, at 3:17 PM, sebb >> > wrote: >>> >>> On Mon, 1 Jun 2020 at 22:42, Craig Russell >>

Re: Emeritus svn operations in roster/workbench

On Mon, 1 Jun 2020 at 23:30, Craig Russell wrote: > > > > > On Jun 1, 2020, at 3:17 PM, sebb wrote: > > > > On Mon, 1 Jun 2020 at 22:42, Craig Russell > > wrote: > >> > >> > >> > >>> On Jun 1, 2020, at 12:28 PM, sebb wrote: > >>> > >>> On Mon, 1 Jun 2020 at 19:59, C

Re: Emeritus svn operations in roster/workbench

On Mon, Jun 1, 2020 at 7:14 PM Craig Russell wrote: > > On Jun 1, 2020, at 3:48 PM, Sam Ruby wrote: > > > > Update: it looks like it fails if not all of the paths have a common root: > > > > svn: E27: Commit failed (details follow): > > svn: E27: Commit can only commit to a single reposit

Re: Emeritus svn operations in roster/workbench

On Jun 1, 2020, at 3:48 PM, Sam Ruby wrote: > > Update: it looks like it fails if not all of the paths have a common root: > > svn: E27: Commit failed (details follow): > svn: E27: Commit can only commit to a single repository at a time. > Are all targets part of the same working copy?

Re: Emeritus svn operations in roster/workbench

Update: it looks like it fails if not all of the paths have a common root: svn: E27: Commit failed (details follow): svn: E27: Commit can only commit to a single repository at a time. Are all targets part of the same working copy? - Sam Ruby On Mon, Jun 1, 2020 at 12:45 PM Sam Ruby wrot

Re: Emeritus svn operations in roster/workbench

> On Jun 1, 2020, at 3:17 PM, sebb wrote: > > On Mon, 1 Jun 2020 at 22:42, Craig Russell > wrote: >> >> >> >>> On Jun 1, 2020, at 12:28 PM, sebb wrote: >>> >>> On Mon, 1 Jun 2020 at 19:59, Craig Russell wrote: I know there are more messages in this

Re: Emeritus svn operations in roster/workbench

On Mon, 1 Jun 2020 at 22:42, Craig Russell wrote: > > > > > On Jun 1, 2020, at 12:28 PM, sebb wrote: > > > > On Mon, 1 Jun 2020 at 19:59, Craig Russell wrote: > >> > >> I know there are more messages in this thread, but this is the most > >> relevant for actually making a change in whimsy. > >>

Re: Emeritus svn operations in roster/workbench

> On Jun 1, 2020, at 12:28 PM, sebb wrote: > > On Mon, 1 Jun 2020 at 19:59, Craig Russell wrote: >> >> I know there are more messages in this thread, but this is the most relevant >> for actually making a change in whimsy. >> >> IIUC, we want to allow _svn.update to take an array of refere

Re: Emeritus svn operations in roster/workbench

On Mon, 1 Jun 2020 at 19:59, Craig Russell wrote: > > I know there are more messages in this thread, but this is the most relevant > for actually making a change in whimsy. > > IIUC, we want to allow _svn.update to take an array of references as the > first argument, and using metadata from else

Re: Emeritus svn operations in roster/workbench

I know there are more messages in this thread, but this is the most relevant for actually making a change in whimsy. IIUC, we want to allow _svn.update to take an array of references as the first argument, and using metadata from elsewhere, check out all of the arguments. The co-routine will ma

Re: Emeritus svn operations in roster/workbench

Wow, let's see git do that! On Mon, 1 Jun 2020 at 11:46, Sam Ruby wrote: > > On Mon, Jun 1, 2020 at 10:13 AM sebb wrote: > > > > It looks like svn commit accepts multiple workspaces. > > Seems to work! Learned something new! > > rubys@rubix:~/svn$ touch foundation/testfile documents/testfile >

Re: Emeritus svn operations in roster/workbench

On Mon, Jun 1, 2020 at 10:13 AM sebb wrote: > > It looks like svn commit accepts multiple workspaces. Seems to work! Learned something new! rubys@rubix:~/svn$ touch foundation/testfile documents/testfile rubys@rubix:~/svn$ svn add foundation/testfile documents/testfile A foundation/test

Re: Emeritus svn operations in roster/workbench

On Mon, 1 Jun 2020 at 13:20, Sam Ruby wrote: > > My feeling is mixed. > > I am not a fan of emeritus-* directories littering the > private/documents directory. Making them subfolders of an Emeritus > folder appeals to me. > > Like Sebb, I'd also think twice before considering moving members.txt.

Re: Emeritus svn operations in roster/workbench

My feeling is mixed. I am not a fan of emeritus-* directories littering the private/documents directory. Making them subfolders of an Emeritus folder appeals to me. Like Sebb, I'd also think twice before considering moving members.txt. That being said, the idea of a single, atomic, commit appea

Re: Emeritus svn operations in roster/workbench

On Sun, 31 May 2020 at 20:03, Craig Russell wrote: > > The following is excerpted from memstat.json.rb. It assumes that we have > moved all of the emeritus files from subdirectories of documents to > subdirectories of documents/Emeritus. > > EMERITUS_DIR = ASF::SVN['documents/Emeritus'] > ... af

Re: Emeritus svn operations in roster/workbench

The following is excerpted from memstat.json.rb. It assumes that we have moved all of the emeritus files from subdirectories of documents to subdirectories of documents/Emeritus. EMERITUS_DIR = ASF::SVN['documents/Emeritus'] ... after the update of members.txt # update the emeritus files if

Re: Emeritus svn operations in roster/workbench

> On May 31, 2020, at 10:36 AM, Craig Russell wrote: > > > >> On May 31, 2020, at 5:55 AM, Sam Ruby > > wrote: >> >> On Sun, May 31, 2020 at 12:50 AM Craig Russell > > wrote: >>> >>> So now I just need an example of svn code execut

Re: Emeritus svn operations in roster/workbench

> On May 31, 2020, at 5:55 AM, Sam Ruby wrote: > > On Sun, May 31, 2020 at 12:50 AM Craig Russell > wrote: >> >> So now I just need an example of svn code executed with no update block and >> some code executed inside the update block. > > Publishing minutes aft

Re: Emeritus svn operations in roster/workbench

On Sun, May 31, 2020 at 12:50 AM Craig Russell wrote: > > So now I just need an example of svn code executed with no update block and > some code executed inside the update block. Publishing minutes after a board meeting involves a number of updates to different svn repositories: https://github

Re: Emeritus svn operations in roster/workbench

On Sun, 31 May 2020 at 05:50, Craig Russell wrote: > > > > > On May 30, 2020, at 6:21 PM, Sam Ruby wrote: > > > > On Sat, May 30, 2020 at 3:08 PM Craig Russell > > wrote: > >> > >>> On May 29, 2020, at 3:17 AM, sebb wrote: > >>> > >>> On Fri, 29 May 2020 at 00:49, C

Re: Emeritus svn operations in roster/workbench

> On May 30, 2020, at 6:21 PM, Sam Ruby wrote: > > On Sat, May 30, 2020 at 3:08 PM Craig Russell > wrote: >> >>> On May 29, 2020, at 3:17 AM, sebb wrote: >>> >>> On Fri, 29 May 2020 at 00:49, Craig Russell wrote: It looks like the best approach is to

Re: Emeritus svn operations in roster/workbench

On Sat, May 30, 2020 at 3:08 PM Craig Russell wrote: > > > On May 29, 2020, at 3:17 AM, sebb wrote: > > > > On Fri, 29 May 2020 at 00:49, Craig Russell wrote: > >> > >> It looks like the best approach is to do the svn operations in two steps: > >> > >> 1. Update the svn foundation/members.txt ba

Re: Emeritus svn operations in roster/workbench

> On May 29, 2020, at 3:17 AM, sebb wrote: > > On Fri, 29 May 2020 at 00:49, Craig Russell wrote: >> >> It looks like the best approach is to do the svn operations in two steps: >> >> 1. Update the svn foundation/members.txt based on the request (active, >> emeritus, deceased) which is alre

Re: Emeritus svn operations in roster/workbench

On Fri, 29 May 2020 at 00:49, Craig Russell wrote: > > It looks like the best approach is to do the svn operations in two steps: > > 1. Update the svn foundation/members.txt based on the request (active, > emeritus, deceased) which is already in place. > 2. Perform the moves in svn documents > (

Emeritus svn operations in roster/workbench

It looks like the best approach is to do the svn operations in two steps: 1. Update the svn foundation/members.txt based on the request (active, emeritus, deceased) which is already in place. 2. Perform the moves in svn documents (emeritus-request-received>emeritus-request-rescinded, emeritus-r