| 1 Oct 2021 |
aciceri | 0. master | 16:53:04 |
@timdeh:matrix.org | *
- master!
| 16:54:10 |
@gtrunsec:matrix.org | 1. main | 16:57:38 |
ultranix |
- master
| 17:26:46 |
@kraftnix:matrix.org | 1. main | 17:35:25 |
David Arnold (blaggacao) | Main comes out on TV today: "I'll promise to be a good branch for all users!" 😆 | 18:11:55 |
ultranix | Micro$oft wins... again | 18:12:31 |
yusdacra | I don't think my client supports polls but | 18:13:28 |
yusdacra |
- main
| 18:13:31 |
yusdacra | (c'mon, it's 2 characters shorter! xD) | 18:13:54 |
@kraftnix:matrix.org | My main (ha) complaint was not with the branch name but that it just "happened" without notice and it took me some time to realise I wasn't on the default branch anymore. | 19:46:26 |
Pacman99 | Agreed it was done without warning and without any discussion | 19:47:50 |
Pacman99 | No matter what we vote, I'll create a pinned issue with the announcement of the branch rename. And if we want to go further we can add a note at the top of the readme. | 19:48:42 |
| 2 Oct 2021 |
@danielphan.2003:matrix.org |
- main
| 08:39:07 |
Pacman99 | Ok so it looks like we're switching devos to main, I can do that later today. | 19:08:46 |
Pacman99 | The vote looks to be 7-3 | 19:09:02 |
Pacman99 | I can put a message in that pinned issue like this:
"We are switching the main branch for devos to be called 'main', because it looks like git and github are moving towards that standard and main is a more descriptive name for the purpose of that branch" | 19:10:18 |
Pacman99 | * I can put a message in that pinned issue like this:
"We are switching the main branch for devos to be called 'main', because it looks like git and github are moving towards that standard and main is a more descriptive name for the purpose of that branch. Also its two letters shorter!" | 19:11:14 |
| Maksim left the room. | 19:11:53 |
| 3 Oct 2021 |
Pacman99 | https://github.com/divnix/devos/issues/384 | 01:20:16 |
David Arnold (blaggacao) | Pacman99: an alternative to mergeAny? https://gist.github.com/blaggacao/050483417bcab6a5cd126152b0187314 | 01:20:53 |
Pacman99 | In reply to @blaggacao:matrix.org Pacman99: an alternative to mergeAny? https://gist.github.com/blaggacao/050483417bcab6a5cd126152b0187314 I think so, it looks to be somewhat similar to recursiveUpdate | 01:24:07 |
Pacman99 | Also I like the type-checking | 01:24:12 |
David Arnold (blaggacao) | I kind of expanded on recursiveUpdate :sm | 01:24:43 |
David Arnold (blaggacao) | * I kind of expanded on recursiveUpdate :smile: | 01:24:49 |
David Arnold (blaggacao) | # assuming lhs are nomad job declarations
dataMerge.merge lhs {
backend.Job.Constraints =
dataMerge.append [ (constrainToAwsInstance "i-061eb00419f0ad0a6") ];
}
| 01:27:59 |
David Arnold (blaggacao) | * # assuming lhs are nomad job declarations
dataMerge.merge lhs {
backend.Job.Constraints =
dataMerge.append [ (constrainToAwsInstance "i-061eb00419f0ad0a6") ];
}
| 01:28:29 |
David Arnold (blaggacao) | * # assuming lhs are nomad job declarations
dataMerge.merge lhs {
backend.Job.Constraints =
dataMerge.append [ (constrainToAwsInstance "i-061eb00419fa6") ];
}
| 01:28:41 |
yusdacra | In reply to @pachumicchu:myrdd.info I can put a message in that pinned issue like this: "We are switching the main branch for devos to be called 'main', because it looks like git and github are moving towards that standard and main is a more descriptive name for the purpose of that branch. Also its two letters shorter!" I wonder if setting up a mail system would work for communicating these changes to users. Something like having bud mail, and executing it when the user switches to their devos config directory, so they are kept up-to-date always. The implementation could be as simple as just checking an RSS feed. | 07:21:33 |
aciceri | 0. master | 10:19:43 |