Re: [Mesa-dev] Rename "master" branch to "main"?
On Monday, 2020-08-03 13:42:28 -0500, Jason Ekstrand wrote: > On Mon, Aug 3, 2020 at 1:38 PM Eric Engestrom wrote: > > > > On Monday, 2020-08-03 13:31:19 -0500, Jason Ekstrand wrote: > > > On Mon, Aug 3, 2020 at 1:24 PM Eric Engestrom wrote: > > > > > > > > On Monday, 2020-08-03 10:30:29 -0500, Jason Ekstrand wrote: > > > > > All, > > > > > > > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > > > > chatter around inclusive language in software. While mesa doesn't > > > > > provide a whole lot of documentation (hah!), we do have a website, a > > > > > code-base, and a git repo and this is something that we, as a project > > > > > should consider. > > > > > > > > > > What I'm proposing today is simply re-naming the primary Git branch > > > > > from "master" to "main". Why "main"? Because that's what GitHub has > > > > > chosen "main" as their new default branch name and so it sounds to me > > > > > like the most likely new default. > > > > > > > > > > As far as impact on the project goes, if and when we rename the > > > > > primary branch, the old "master" branch will be locked (no > > > > > pushing/merging allowed) and all MRs will have to be re-targeted > > > > > against the new branch. Fortunately, that's very easy to do. You > > > > > just edit the MR and there's a little drop-down box at the top for > > > > > which branch it targets. I just tested this with one of mine and it > > > > > seems to work ok. > > > > > > > > > > As far as other bits of language in the code-base, I'm happy to see > > > > > those cleaned up as people have opportunity. I'm not aware of any > > > > > particularly egregious offenders. However, changing the name of the > > > > > primary branch is something which will cause a brief hiccup in > > > > > people's development process and so warrants broader discussion. > > > > > > > > > > Thoughts? > > > > > > > > Definite +1 for me on the idea, but we do have a lot of tools and > > > > processes with `master` baked in. I'll try and have a look at everything > > > > to make sure everything supports the transition (some things will need > > > > to support both the old and new names), but assuming no issue there this > > > > would be a really good thing to do, and `main` is a good name. > > > > > > I did some grepping and I noticed that as well. Some of the tools > > > such as the khronos sync scripts will have to change if/when Khronos > > > repos make a similar transition. I expect that to happen but don't > > > have a timeline. I'll try to keep you posted on those. > > > > The external things like Khronos should be easy enough to handle, I was > > more concerned about internal things like the stable branches. > > > > > > > > For the internal ones, if you wanted to make a MR for it, we can > > > either land it with support for both ahead of the switch or we can > > > make it the first commit that goes on the new "main" branch. In any > > > case, I'm not in so much of a hurry that I think we need to make the > > > switch ahead of getting tooling ready. > > > > No hurry either... except a branchpoint like the one happening in 2 > > days is the perfect time to minimize issues, as we could have eg. > > `master` for VERSION<20.2 and `main` for VERSION>=20.2 which would > > make it trivial for tools to know which branch name to use based on > > the VERSION file. > > Pardon me for being a bit daft but what's the issue there? "main" > will contain all of the commits in "master" with exactly the same > SHAs. The tools shouldn't have to make a distinction, I wouldn't > think. What am I missing? Heh, I'm the daft one :] You're right, there's absolutely no issue here! ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 1:38 PM Eric Engestrom wrote: > > On Monday, 2020-08-03 13:31:19 -0500, Jason Ekstrand wrote: > > On Mon, Aug 3, 2020 at 1:24 PM Eric Engestrom wrote: > > > > > > On Monday, 2020-08-03 10:30:29 -0500, Jason Ekstrand wrote: > > > > All, > > > > > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > > > chatter around inclusive language in software. While mesa doesn't > > > > provide a whole lot of documentation (hah!), we do have a website, a > > > > code-base, and a git repo and this is something that we, as a project > > > > should consider. > > > > > > > > What I'm proposing today is simply re-naming the primary Git branch > > > > from "master" to "main". Why "main"? Because that's what GitHub has > > > > chosen "main" as their new default branch name and so it sounds to me > > > > like the most likely new default. > > > > > > > > As far as impact on the project goes, if and when we rename the > > > > primary branch, the old "master" branch will be locked (no > > > > pushing/merging allowed) and all MRs will have to be re-targeted > > > > against the new branch. Fortunately, that's very easy to do. You > > > > just edit the MR and there's a little drop-down box at the top for > > > > which branch it targets. I just tested this with one of mine and it > > > > seems to work ok. > > > > > > > > As far as other bits of language in the code-base, I'm happy to see > > > > those cleaned up as people have opportunity. I'm not aware of any > > > > particularly egregious offenders. However, changing the name of the > > > > primary branch is something which will cause a brief hiccup in > > > > people's development process and so warrants broader discussion. > > > > > > > > Thoughts? > > > > > > Definite +1 for me on the idea, but we do have a lot of tools and > > > processes with `master` baked in. I'll try and have a look at everything > > > to make sure everything supports the transition (some things will need > > > to support both the old and new names), but assuming no issue there this > > > would be a really good thing to do, and `main` is a good name. > > > > I did some grepping and I noticed that as well. Some of the tools > > such as the khronos sync scripts will have to change if/when Khronos > > repos make a similar transition. I expect that to happen but don't > > have a timeline. I'll try to keep you posted on those. > > The external things like Khronos should be easy enough to handle, I was > more concerned about internal things like the stable branches. > > > > > For the internal ones, if you wanted to make a MR for it, we can > > either land it with support for both ahead of the switch or we can > > make it the first commit that goes on the new "main" branch. In any > > case, I'm not in so much of a hurry that I think we need to make the > > switch ahead of getting tooling ready. > > No hurry either... except a branchpoint like the one happening in 2 > days is the perfect time to minimize issues, as we could have eg. > `master` for VERSION<20.2 and `main` for VERSION>=20.2 which would > make it trivial for tools to know which branch name to use based on > the VERSION file. Pardon me for being a bit daft but what's the issue there? "main" will contain all of the commits in "master" with exactly the same SHAs. The tools shouldn't have to make a distinction, I wouldn't think. What am I missing? --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Monday, 2020-08-03 13:31:19 -0500, Jason Ekstrand wrote: > On Mon, Aug 3, 2020 at 1:24 PM Eric Engestrom wrote: > > > > On Monday, 2020-08-03 10:30:29 -0500, Jason Ekstrand wrote: > > > All, > > > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > > chatter around inclusive language in software. While mesa doesn't > > > provide a whole lot of documentation (hah!), we do have a website, a > > > code-base, and a git repo and this is something that we, as a project > > > should consider. > > > > > > What I'm proposing today is simply re-naming the primary Git branch > > > from "master" to "main". Why "main"? Because that's what GitHub has > > > chosen "main" as their new default branch name and so it sounds to me > > > like the most likely new default. > > > > > > As far as impact on the project goes, if and when we rename the > > > primary branch, the old "master" branch will be locked (no > > > pushing/merging allowed) and all MRs will have to be re-targeted > > > against the new branch. Fortunately, that's very easy to do. You > > > just edit the MR and there's a little drop-down box at the top for > > > which branch it targets. I just tested this with one of mine and it > > > seems to work ok. > > > > > > As far as other bits of language in the code-base, I'm happy to see > > > those cleaned up as people have opportunity. I'm not aware of any > > > particularly egregious offenders. However, changing the name of the > > > primary branch is something which will cause a brief hiccup in > > > people's development process and so warrants broader discussion. > > > > > > Thoughts? > > > > Definite +1 for me on the idea, but we do have a lot of tools and > > processes with `master` baked in. I'll try and have a look at everything > > to make sure everything supports the transition (some things will need > > to support both the old and new names), but assuming no issue there this > > would be a really good thing to do, and `main` is a good name. > > I did some grepping and I noticed that as well. Some of the tools > such as the khronos sync scripts will have to change if/when Khronos > repos make a similar transition. I expect that to happen but don't > have a timeline. I'll try to keep you posted on those. The external things like Khronos should be easy enough to handle, I was more concerned about internal things like the stable branches. > > For the internal ones, if you wanted to make a MR for it, we can > either land it with support for both ahead of the switch or we can > make it the first commit that goes on the new "main" branch. In any > case, I'm not in so much of a hurry that I think we need to make the > switch ahead of getting tooling ready. No hurry either... except a branchpoint like the one happening in 2 days is the perfect time to minimize issues, as we could have eg. `master` for VERSION<20.2 and `main` for VERSION>=20.2 which would make it trivial for tools to know which branch name to use based on the VERSION file. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 1:24 PM Eric Engestrom wrote: > > On Monday, 2020-08-03 10:30:29 -0500, Jason Ekstrand wrote: > > All, > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > chatter around inclusive language in software. While mesa doesn't > > provide a whole lot of documentation (hah!), we do have a website, a > > code-base, and a git repo and this is something that we, as a project > > should consider. > > > > What I'm proposing today is simply re-naming the primary Git branch > > from "master" to "main". Why "main"? Because that's what GitHub has > > chosen "main" as their new default branch name and so it sounds to me > > like the most likely new default. > > > > As far as impact on the project goes, if and when we rename the > > primary branch, the old "master" branch will be locked (no > > pushing/merging allowed) and all MRs will have to be re-targeted > > against the new branch. Fortunately, that's very easy to do. You > > just edit the MR and there's a little drop-down box at the top for > > which branch it targets. I just tested this with one of mine and it > > seems to work ok. > > > > As far as other bits of language in the code-base, I'm happy to see > > those cleaned up as people have opportunity. I'm not aware of any > > particularly egregious offenders. However, changing the name of the > > primary branch is something which will cause a brief hiccup in > > people's development process and so warrants broader discussion. > > > > Thoughts? > > Definite +1 for me on the idea, but we do have a lot of tools and > processes with `master` baked in. I'll try and have a look at everything > to make sure everything supports the transition (some things will need > to support both the old and new names), but assuming no issue there this > would be a really good thing to do, and `main` is a good name. I did some grepping and I noticed that as well. Some of the tools such as the khronos sync scripts will have to change if/when Khronos repos make a similar transition. I expect that to happen but don't have a timeline. I'll try to keep you posted on those. For the internal ones, if you wanted to make a MR for it, we can either land it with support for both ahead of the switch or we can make it the first commit that goes on the new "main" branch. In any case, I'm not in so much of a hurry that I think we need to make the switch ahead of getting tooling ready. --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Monday, 2020-08-03 10:30:29 -0500, Jason Ekstrand wrote: > All, > > I'm sure by now you've all seen the articles, LKML mails, and other > chatter around inclusive language in software. While mesa doesn't > provide a whole lot of documentation (hah!), we do have a website, a > code-base, and a git repo and this is something that we, as a project > should consider. > > What I'm proposing today is simply re-naming the primary Git branch > from "master" to "main". Why "main"? Because that's what GitHub has > chosen "main" as their new default branch name and so it sounds to me > like the most likely new default. > > As far as impact on the project goes, if and when we rename the > primary branch, the old "master" branch will be locked (no > pushing/merging allowed) and all MRs will have to be re-targeted > against the new branch. Fortunately, that's very easy to do. You > just edit the MR and there's a little drop-down box at the top for > which branch it targets. I just tested this with one of mine and it > seems to work ok. > > As far as other bits of language in the code-base, I'm happy to see > those cleaned up as people have opportunity. I'm not aware of any > particularly egregious offenders. However, changing the name of the > primary branch is something which will cause a brief hiccup in > people's development process and so warrants broader discussion. > > Thoughts? Definite +1 for me on the idea, but we do have a lot of tools and processes with `master` baked in. I'll try and have a look at everything to make sure everything supports the transition (some things will need to support both the old and new names), but assuming no issue there this would be a really good thing to do, and `main` is a good name. Thanks for starting the conversation! ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On 8/3/20 8:30 AM, Jason Ekstrand wrote: > All, > > I'm sure by now you've all seen the articles, LKML mails, and other > chatter around inclusive language in software. While mesa doesn't > provide a whole lot of documentation (hah!), we do have a website, a > code-base, and a git repo and this is something that we, as a project > should consider. > > What I'm proposing today is simply re-naming the primary Git branch > from "master" to "main". Why "main"? Because that's what GitHub has > chosen "main" as their new default branch name and so it sounds to me > like the most likely new default. > > As far as impact on the project goes, if and when we rename the > primary branch, the old "master" branch will be locked (no > pushing/merging allowed) and all MRs will have to be re-targeted > against the new branch. Fortunately, that's very easy to do. You > just edit the MR and there's a little drop-down box at the top for > which branch it targets. I just tested this with one of mine and it > seems to work ok. > > As far as other bits of language in the code-base, I'm happy to see > those cleaned up as people have opportunity. I'm not aware of any > particularly egregious offenders. However, changing the name of the > primary branch is something which will cause a brief hiccup in > people's development process and so warrants broader discussion. I looked at this a week or so ago. My recollection is that there were a couple other instanced of master (that were references to field names in a DRM header) and a couple instances of whitelist / blacklist. Coordinating renaming the field from the DRM header will be fun, but everything else should be trivial... and would make for good newbie tasks. :) > Thoughts? > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 12:51 PM Erik Faye-Lund wrote: > > On Mon, 2020-08-03 at 12:48 -0500, Jason Ekstrand wrote: > > On Mon, Aug 3, 2020 at 12:42 PM Erik Faye-Lund > > wrote: > > > On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote: > > > > All, > > > > > > > > I'm sure by now you've all seen the articles, LKML mails, and > > > > other > > > > chatter around inclusive language in software. While mesa > > > > doesn't > > > > provide a whole lot of documentation (hah!), we do have a > > > > website, a > > > > code-base, and a git repo and this is something that we, as a > > > > project > > > > should consider. > > > > > > > > What I'm proposing today is simply re-naming the primary Git > > > > branch > > > > from "master" to "main". Why "main"? Because that's what GitHub > > > > has > > > > chosen "main" as their new default branch name and so it sounds > > > > to me > > > > like the most likely new default. > > > > > > > > As far as impact on the project goes, if and when we rename the > > > > primary branch, the old "master" branch will be locked (no > > > > pushing/merging allowed) and all MRs will have to be re-targeted > > > > against the new branch. Fortunately, that's very easy to > > > > do. You > > > > just edit the MR and there's a little drop-down box at the top > > > > for > > > > which branch it targets. I just tested this with one of mine and > > > > it > > > > seems to work ok. > > > > > > > > As far as other bits of language in the code-base, I'm happy to > > > > see > > > > those cleaned up as people have opportunity. I'm not aware of > > > > any > > > > particularly egregious offenders. However, changing the name of > > > > the > > > > primary branch is something which will cause a brief hiccup in > > > > people's development process and so warrants broader discussion. > > > > > > > > Thoughts? > > > > > > > > > > I'm all for renaming it, but I'm a bit worried about doing it in a > > > way > > > where we don't break all merge-requests... > > > > > > As far as I know, GitLab doesn't allow changing the target-branch > > > of a > > > merge-request, so all pending merge-requests would all of a sudden > > > point to the wrong branch. > > > > No and yes. It doesn't have any way to mass-edit merge requests to > > re-target them. (It does have a mass-edit tool but it doesn't > > support > > that). However, it does support re-targetting individual merge > > requests. I even gave instructions for doing so in my first e-mail. > > :-) > > > > Thanks for pointing that out, I feel kinda stupid now. I was looking > for that feature in the past, and couldn't find it, but surely there it > is! No worries. I was 100% sure it wasn't there too until I looked for it today. Maybe it was added recently? > I guess I should have read more carefully. Updating every merge request > manually should be a totally OK compromise IMO. Cool. --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, 2020-08-03 at 12:48 -0500, Jason Ekstrand wrote: > On Mon, Aug 3, 2020 at 12:42 PM Erik Faye-Lund > wrote: > > On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote: > > > All, > > > > > > I'm sure by now you've all seen the articles, LKML mails, and > > > other > > > chatter around inclusive language in software. While mesa > > > doesn't > > > provide a whole lot of documentation (hah!), we do have a > > > website, a > > > code-base, and a git repo and this is something that we, as a > > > project > > > should consider. > > > > > > What I'm proposing today is simply re-naming the primary Git > > > branch > > > from "master" to "main". Why "main"? Because that's what GitHub > > > has > > > chosen "main" as their new default branch name and so it sounds > > > to me > > > like the most likely new default. > > > > > > As far as impact on the project goes, if and when we rename the > > > primary branch, the old "master" branch will be locked (no > > > pushing/merging allowed) and all MRs will have to be re-targeted > > > against the new branch. Fortunately, that's very easy to > > > do. You > > > just edit the MR and there's a little drop-down box at the top > > > for > > > which branch it targets. I just tested this with one of mine and > > > it > > > seems to work ok. > > > > > > As far as other bits of language in the code-base, I'm happy to > > > see > > > those cleaned up as people have opportunity. I'm not aware of > > > any > > > particularly egregious offenders. However, changing the name of > > > the > > > primary branch is something which will cause a brief hiccup in > > > people's development process and so warrants broader discussion. > > > > > > Thoughts? > > > > > > > I'm all for renaming it, but I'm a bit worried about doing it in a > > way > > where we don't break all merge-requests... > > > > As far as I know, GitLab doesn't allow changing the target-branch > > of a > > merge-request, so all pending merge-requests would all of a sudden > > point to the wrong branch. > > No and yes. It doesn't have any way to mass-edit merge requests to > re-target them. (It does have a mass-edit tool but it doesn't > support > that). However, it does support re-targetting individual merge > requests. I even gave instructions for doing so in my first e-mail. > :-) > Thanks for pointing that out, I feel kinda stupid now. I was looking for that feature in the past, and couldn't find it, but surely there it is! I guess I should have read more carefully. Updating every merge request manually should be a totally OK compromise IMO. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 12:42 PM Erik Faye-Lund wrote: > > On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote: > > All, > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > chatter around inclusive language in software. While mesa doesn't > > provide a whole lot of documentation (hah!), we do have a website, a > > code-base, and a git repo and this is something that we, as a project > > should consider. > > > > What I'm proposing today is simply re-naming the primary Git branch > > from "master" to "main". Why "main"? Because that's what GitHub has > > chosen "main" as their new default branch name and so it sounds to me > > like the most likely new default. > > > > As far as impact on the project goes, if and when we rename the > > primary branch, the old "master" branch will be locked (no > > pushing/merging allowed) and all MRs will have to be re-targeted > > against the new branch. Fortunately, that's very easy to do. You > > just edit the MR and there's a little drop-down box at the top for > > which branch it targets. I just tested this with one of mine and it > > seems to work ok. > > > > As far as other bits of language in the code-base, I'm happy to see > > those cleaned up as people have opportunity. I'm not aware of any > > particularly egregious offenders. However, changing the name of the > > primary branch is something which will cause a brief hiccup in > > people's development process and so warrants broader discussion. > > > > Thoughts? > > > > I'm all for renaming it, but I'm a bit worried about doing it in a way > where we don't break all merge-requests... > > As far as I know, GitLab doesn't allow changing the target-branch of a > merge-request, so all pending merge-requests would all of a sudden > point to the wrong branch. No and yes. It doesn't have any way to mass-edit merge requests to re-target them. (It does have a mass-edit tool but it doesn't support that). However, it does support re-targetting individual merge requests. I even gave instructions for doing so in my first e-mail. :-) --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, 3 Aug 2020 at 18:42, Erik Faye-Lund wrote: > > On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote: > > All, > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > chatter around inclusive language in software. While mesa doesn't > > provide a whole lot of documentation (hah!), we do have a website, a > > code-base, and a git repo and this is something that we, as a project > > should consider. > > > > What I'm proposing today is simply re-naming the primary Git branch > > from "master" to "main". Why "main"? Because that's what GitHub has > > chosen "main" as their new default branch name and so it sounds to me > > like the most likely new default. > > > > As far as impact on the project goes, if and when we rename the > > primary branch, the old "master" branch will be locked (no > > pushing/merging allowed) and all MRs will have to be re-targeted > > against the new branch. Fortunately, that's very easy to do. You > > just edit the MR and there's a little drop-down box at the top for > > which branch it targets. I just tested this with one of mine and it > > seems to work ok. > > > > As far as other bits of language in the code-base, I'm happy to see > > those cleaned up as people have opportunity. I'm not aware of any > > particularly egregious offenders. However, changing the name of the > > primary branch is something which will cause a brief hiccup in > > people's development process and so warrants broader discussion. > > > > Thoughts? > > > > I'm all for renaming it, but I'm a bit worried about doing it in a way > where we don't break all merge-requests... > > As far as I know, GitLab doesn't allow changing the target-branch of a > merge-request, so all pending merge-requests would all of a sudden > point to the wrong branch. Unless we have a a plan for somehow making > sure both branches are updated in lock-step in a grace-period or > something like that... > > I dunno. Does anyone have any great ideas for avoiding this problem? > Is that one that can be fixed in GitLab itself? I imagine a lot of projects are going to be making similar changes ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote: > All, > > I'm sure by now you've all seen the articles, LKML mails, and other > chatter around inclusive language in software. While mesa doesn't > provide a whole lot of documentation (hah!), we do have a website, a > code-base, and a git repo and this is something that we, as a project > should consider. > > What I'm proposing today is simply re-naming the primary Git branch > from "master" to "main". Why "main"? Because that's what GitHub has > chosen "main" as their new default branch name and so it sounds to me > like the most likely new default. > > As far as impact on the project goes, if and when we rename the > primary branch, the old "master" branch will be locked (no > pushing/merging allowed) and all MRs will have to be re-targeted > against the new branch. Fortunately, that's very easy to do. You > just edit the MR and there's a little drop-down box at the top for > which branch it targets. I just tested this with one of mine and it > seems to work ok. > > As far as other bits of language in the code-base, I'm happy to see > those cleaned up as people have opportunity. I'm not aware of any > particularly egregious offenders. However, changing the name of the > primary branch is something which will cause a brief hiccup in > people's development process and so warrants broader discussion. > > Thoughts? > I'm all for renaming it, but I'm a bit worried about doing it in a way where we don't break all merge-requests... As far as I know, GitLab doesn't allow changing the target-branch of a merge-request, so all pending merge-requests would all of a sudden point to the wrong branch. Unless we have a a plan for somehow making sure both branches are updated in lock-step in a grace-period or something like that... I dunno. Does anyone have any great ideas for avoiding this problem? ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 10:16 AM Eric Anholt wrote: > > On Mon, Aug 3, 2020 at 8:30 AM Jason Ekstrand wrote: > > > > All, > > > > I'm sure by now you've all seen the articles, LKML mails, and other > > chatter around inclusive language in software. While mesa doesn't > > provide a whole lot of documentation (hah!), we do have a website, a > > code-base, and a git repo and this is something that we, as a project > > should consider. > > > > What I'm proposing today is simply re-naming the primary Git branch > > from "master" to "main". Why "main"? Because that's what GitHub has > > chosen "main" as their new default branch name and so it sounds to me > > like the most likely new default. > > > > As far as impact on the project goes, if and when we rename the > > primary branch, the old "master" branch will be locked (no > > pushing/merging allowed) and all MRs will have to be re-targeted > > against the new branch. Fortunately, that's very easy to do. You > > just edit the MR and there's a little drop-down box at the top for > > which branch it targets. I just tested this with one of mine and it > > seems to work ok. > > > > As far as other bits of language in the code-base, I'm happy to see > > those cleaned up as people have opportunity. I'm not aware of any > > particularly egregious offenders. However, changing the name of the > > primary branch is something which will cause a brief hiccup in > > people's development process and so warrants broader discussion. > > > > Thoughts? > > +1 from me Let's go! > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 8:30 AM Jason Ekstrand wrote: > > All, > > I'm sure by now you've all seen the articles, LKML mails, and other > chatter around inclusive language in software. While mesa doesn't > provide a whole lot of documentation (hah!), we do have a website, a > code-base, and a git repo and this is something that we, as a project > should consider. > > What I'm proposing today is simply re-naming the primary Git branch > from "master" to "main". Why "main"? Because that's what GitHub has > chosen "main" as their new default branch name and so it sounds to me > like the most likely new default. > > As far as impact on the project goes, if and when we rename the > primary branch, the old "master" branch will be locked (no > pushing/merging allowed) and all MRs will have to be re-targeted > against the new branch. Fortunately, that's very easy to do. You > just edit the MR and there's a little drop-down box at the top for > which branch it targets. I just tested this with one of mine and it > seems to work ok. > > As far as other bits of language in the code-base, I'm happy to see > those cleaned up as people have opportunity. I'm not aware of any > particularly egregious offenders. However, changing the name of the > primary branch is something which will cause a brief hiccup in > people's development process and so warrants broader discussion. > > Thoughts? +1 from me ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] piglit/mesa marge access => DONE
Thanks all! On Mon, Aug 3, 2020, 12:20 PM Kenneth Graunke wrote: > On Friday, July 31, 2020 7:14:49 AM PDT Mike Blumenkrantz wrote: > > Hi, > > > > I'd like to request marge access for the piglit and mesa gitlab projects. > > I've been contributing a number of patches here (primarily to > > zink/gallium), and this would be useful in my continued work. > > > > > > Regards, > > Mike (zmike) > > > > +1 from me! > > I just granted you Developer access to gitlab.freedesktop.org/mesa, > including Mesa, Piglit, and other related projects. > > --Ken > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On 2020-08-03 6:15 p.m., Jason Ekstrand wrote: > On Mon, Aug 3, 2020 at 11:12 AM Kenneth Graunke wrote: >> >> Seems reasonable to me...in the old Subversion days, we called it >> 'trunk'...then 'master' with Git...but calling the main development >> branch 'main' is arguably the simplest and most descriptive term. >> >> One thing we'll have to coordinate: getting Gitlab CI / Marge and the >> Intel Mesa CI to switch over at the right time, so we don't end up >> breaking/interrupting those services. Should be easy, just requires >> a bit of coordination. > > Yup, I threw Daniel onto the CC of this e-mail explicitly for that > reason. We may also want to coordinate with the rest of fd.o so that > everyone chooses the same new mainline branch name. I just added > Michel to the CC as he's doing lots of CI stuff and might be a good > person to help coordinate there. AFAICT only the '$CI_COMMIT_REF_NAME == "master"' test in the .gitlab-ci.yml "pages" job definition needs to be extended / changed to cover the new branch name as well / instead. Other than that, no changes should be necessary for Marge or GitLab CI in general. (Failure to adapt the pages job means the public website wouldn't get updated to reflect changes in the tree) -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
Seems reasonable to me...in the old Subversion days, we called it 'trunk'...then 'master' with Git...but calling the main development branch 'main' is arguably the simplest and most descriptive term. One thing we'll have to coordinate: getting Gitlab CI / Marge and the Intel Mesa CI to switch over at the right time, so we don't end up breaking/interrupting those services. Should be easy, just requires a bit of coordination. --Ken signature.asc Description: This is a digitally signed message part. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] piglit/mesa marge access => DONE
On Friday, July 31, 2020 7:14:49 AM PDT Mike Blumenkrantz wrote: > Hi, > > I'd like to request marge access for the piglit and mesa gitlab projects. > I've been contributing a number of patches here (primarily to > zink/gallium), and this would be useful in my continued work. > > > Regards, > Mike (zmike) > +1 from me! I just granted you Developer access to gitlab.freedesktop.org/mesa, including Mesa, Piglit, and other related projects. --Ken signature.asc Description: This is a digitally signed message part. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
On Mon, Aug 3, 2020 at 11:12 AM Kenneth Graunke wrote: > > Seems reasonable to me...in the old Subversion days, we called it > 'trunk'...then 'master' with Git...but calling the main development > branch 'main' is arguably the simplest and most descriptive term. > > One thing we'll have to coordinate: getting Gitlab CI / Marge and the > Intel Mesa CI to switch over at the right time, so we don't end up > breaking/interrupting those services. Should be easy, just requires > a bit of coordination. Yup, I threw Daniel onto the CC of this e-mail explicitly for that reason. We may also want to coordinate with the rest of fd.o so that everyone chooses the same new mainline branch name. I just added Michel to the CC as he's doing lots of CI stuff and might be a good person to help coordinate there. I certainly don't want to pull the rug out from under anyone. --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Rename "master" branch to "main"?
If it's helpful (I think it is), Google has published the following document as part of their Android developer documentation: https://source.android.com/setup/contribute/respectful-code It provides not only lists of terms but also suggestions for replacements. It's all context-specific, of course, so doing a simple search-and-replace likely isn't going to work. However, I think such documents are helpful for guiding the discussion. --Jason On Mon, Aug 3, 2020 at 10:30 AM Jason Ekstrand wrote: > > All, > > I'm sure by now you've all seen the articles, LKML mails, and other > chatter around inclusive language in software. While mesa doesn't > provide a whole lot of documentation (hah!), we do have a website, a > code-base, and a git repo and this is something that we, as a project > should consider. > > What I'm proposing today is simply re-naming the primary Git branch > from "master" to "main". Why "main"? Because that's what GitHub has > chosen "main" as their new default branch name and so it sounds to me > like the most likely new default. > > As far as impact on the project goes, if and when we rename the > primary branch, the old "master" branch will be locked (no > pushing/merging allowed) and all MRs will have to be re-targeted > against the new branch. Fortunately, that's very easy to do. You > just edit the MR and there's a little drop-down box at the top for > which branch it targets. I just tested this with one of mine and it > seems to work ok. > > As far as other bits of language in the code-base, I'm happy to see > those cleaned up as people have opportunity. I'm not aware of any > particularly egregious offenders. However, changing the name of the > primary branch is something which will cause a brief hiccup in > people's development process and so warrants broader discussion. > > Thoughts? ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Rename "master" branch to "main"?
All, I'm sure by now you've all seen the articles, LKML mails, and other chatter around inclusive language in software. While mesa doesn't provide a whole lot of documentation (hah!), we do have a website, a code-base, and a git repo and this is something that we, as a project should consider. What I'm proposing today is simply re-naming the primary Git branch from "master" to "main". Why "main"? Because that's what GitHub has chosen "main" as their new default branch name and so it sounds to me like the most likely new default. As far as impact on the project goes, if and when we rename the primary branch, the old "master" branch will be locked (no pushing/merging allowed) and all MRs will have to be re-targeted against the new branch. Fortunately, that's very easy to do. You just edit the MR and there's a little drop-down box at the top for which branch it targets. I just tested this with one of mine and it seems to work ok. As far as other bits of language in the code-base, I'm happy to see those cleaned up as people have opportunity. I'm not aware of any particularly egregious offenders. However, changing the name of the primary branch is something which will cause a brief hiccup in people's development process and so warrants broader discussion. Thoughts? ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Gallium: Anybody object to adding a new PIPE_CAP_NIR_ATOMICS_AS_DEREF?
Hi, has anybody any objection to adding a new cap PIPE_CAP_NIR_ATOMICS_AS_DEREF, see: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6025/diffs?commit_id=1e8c3032b96a4878f6fee44aaa10ca341da97e1f Otherwise I'd like to merge this to move forward with r600/nir atomics support, many thanks, Gert ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
