Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
Hagio-san, Bhupesh, (Sorry for delayed response because I had one week vacation last week...) > > -Original Message- > > - Original Message - > > > Dave, > > > > > > > Initially Kazuhito will primarily be handling upstream github duties, > > > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > > > > RHEL maintenance. All three will be involved in the acceptance of > > > > patches posted on this mailing list. Please welcome them in their > > > > new roles; I am confident they will do a terrific job. > > > > > > Maybe, is it better to send patch set via github as PR from now on? I'm > > > now writing > > > zram patch set for x86-64 support. > > > > Hi Daisuke, > > > > Good question -- and one that I shall defer the answer to the new > > maintainers. > > > > Personally, I never accepted git pull requests because I always felt that > > it was more valuable to expose proposed patches to the larger audience > > that make up this mailing list. So when PRs came in, I coerced the > > submitter to use the list. > > I'm thinking that we continue this way as-is and I'd like to do so > because of the same reason Dave says. > > Crash's watchers [1] receives Issues/PR emails, but there are 55 people > now (although the number would increase if we use GitHub mainly), > while the crash-utility mailing list has several hundreds members. > > (And I personally think that it's easier to discuss things via email, > which I'm used to.) > > If it's hard for us to continue the way or using GitHub looks much more > efficient in the future, then we can shift it to a GitHub way. > > [1] https://github.com/crash-utility/crash/watchers > > Thanks, > Kazu I see. I'll send the next patch in this mailing list. Thanks. HATAYAMA, Daisuke -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
Dave, (Sorry for delayed response because I had one week vacation last week...) > - Original Message - > > Dave, > > > > > Initially Kazuhito will primarily be handling upstream github duties, > > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > > > RHEL maintenance. All three will be involved in the acceptance of > > > patches posted on this mailing list. Please welcome them in their > > > new roles; I am confident they will do a terrific job. > > > > Maybe, is it better to send patch set via github as PR from now on? I'm now > > writing > > zram patch set for x86-64 support. > > Hi Daisuke, > > Good question -- and one that I shall defer the answer to the new maintainers. > > Personally, I never accepted git pull requests because I always felt that > it was more valuable to expose proposed patches to the larger audience > that make up this mailing list. So when PRs came in, I coerced the > submitter to use the list. Hagio-san and Bhupesh says they want to keep the current way based the mailing list, and so I'll send the next patch set by email. > > > > > Since the https://people.redhat.com/anderson web page will be > > > decommissioned after my departure, its contents have been moved > > > to be co-located with the crash-utility github site: > > > > > > https://crash-utility.github.io > > > > Do you plan to set a redirection from the current page? Rpm packages for > > crash's extension modules have URL in each rpm information like below and > > need to > > modify it accordingly: > > > > # yum info crash-gcore-command > > Loaded plugins: langpacks, product-id, search-disabled-repos, > > subscription-manager > > Available Packages > > Name: crash-gcore-command > > Arch: x86_64 > > Version : 1.3.1 > > Release : 0.el7 > > Size: 41 k > > Repo: rhel-7-server-rpms/7Server/x86_64 > > Summary : Gcore extension module for the crash utility > > URL : > > http://people.redhat.com/anderson/extensions/crash-gcore-command-1.3.1.tar.gz > > License : GPLv2 > > Description : Command for creating a core dump file of a user-space > > task that > > : was running in a kernel dumpfile. > > Yes, when the packages are updated, the URLs will have to be changed. During > the build > procedure, the package verification will fail if the upstream URL is defunct. > Thanks. I'll make sure that when we update the packages next, and redirection will be helpful. > > > > Also, when I want to release a new version of crash extnesion module, I > > send it to Hagio-san via > > this mailing list as in the past, and then Hagio-san modifies the "crash > > extension modules" page. > > Is this understanding correct? > > Yes, and then Kazu, Liang or Bhupesh will be able to update that page. I see. Thanks. HATAYAMA, Daisuke -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
On Mon 2020-05-04 10:10 -0400, Dave Anderson wrote: Dave, > I want to express my appreciation to all of you who have contributed > patches, both bug fixes and new features, and most importantly, to the > support from users who have kept the crash utility alive for over 20 years > now. It has been my great pleasure to have had the chance to work with > such an extraordinary international cast of characters. I wish you all the best in your retirement. Kind regards, -- Aaron Tomlin -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
On Thu, May 7, 2020 at 8:34 PM HAGIO KAZUHITO(萩尾 一仁) wrote: > > > > Dave, > > > > > > > Initially Kazuhito will primarily be handling upstream github duties, > > > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > > > > RHEL maintenance. All three will be involved in the acceptance of > > > > patches posted on this mailing list. Please welcome them in their > > > > new roles; I am confident they will do a terrific job. > > > > > > Maybe, is it better to send patch set via github as PR from now on? I'm > > > now writing > > > zram patch set for x86-64 support. > > > > Hi Daisuke, > > > > Good question -- and one that I shall defer the answer to the new > > maintainers. > > > > Personally, I never accepted git pull requests because I always felt that > > it was more valuable to expose proposed patches to the larger audience > > that make up this mailing list. So when PRs came in, I coerced the > > submitter to use the list. > > I'm thinking that we continue this way as-is and I'd like to do so > because of the same reason Dave says. > > Crash's watchers [1] receives Issues/PR emails, but there are 55 people > now (although the number would increase if we use GitHub mainly), > while the crash-utility mailing list has several hundreds members. > > (And I personally think that it's easier to discuss things via email, > which I'm used to.) > > If it's hard for us to continue the way or using GitHub looks much more > efficient in the future, then we can shift it to a GitHub way. > > [1] https://github.com/crash-utility/crash/watchers Thanks a lot Dave for introducing us to the rest of the crash-utility users and thanks for all your work in maintaining and managing the crash-utility. It's pretty useful tool to have and its nice to see its user-base increasing so rapidly. I agree with Kazu here, handling patches (for features/bug-fixes) via crash-utility mailing list offer couple of advantages: - It's easier for me to review patches and discuss patches via email. Since I review a variety of other kernel/user-space package related patches, I would prefer handling crash-utility patches in the same way. - Its easier to maintain patch history and ACK process via an email - there are already some automated tools available for them. Also, like Kazu said, this is just a start - if we see issues, we can always jump back to the github way (pull request/bug-repots) in the future. Regards, Bhupesh -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
> -Original Message- > - Original Message - > > Dave, > > > > > Initially Kazuhito will primarily be handling upstream github duties, > > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > > > RHEL maintenance. All three will be involved in the acceptance of > > > patches posted on this mailing list. Please welcome them in their > > > new roles; I am confident they will do a terrific job. > > > > Maybe, is it better to send patch set via github as PR from now on? I'm now > > writing > > zram patch set for x86-64 support. > > Hi Daisuke, > > Good question -- and one that I shall defer the answer to the new maintainers. > > Personally, I never accepted git pull requests because I always felt that > it was more valuable to expose proposed patches to the larger audience > that make up this mailing list. So when PRs came in, I coerced the > submitter to use the list. I'm thinking that we continue this way as-is and I'd like to do so because of the same reason Dave says. Crash's watchers [1] receives Issues/PR emails, but there are 55 people now (although the number would increase if we use GitHub mainly), while the crash-utility mailing list has several hundreds members. (And I personally think that it's easier to discuss things via email, which I'm used to.) If it's hard for us to continue the way or using GitHub looks much more efficient in the future, then we can shift it to a GitHub way. [1] https://github.com/crash-utility/crash/watchers Thanks, Kazu > > > > > > Since the https://people.redhat.com/anderson web page will be > > > decommissioned after my departure, its contents have been moved > > > to be co-located with the crash-utility github site: > > > > > > https://crash-utility.github.io > > > > Do you plan to set a redirection from the current page? Rpm packages for > > crash's extension modules have URL in each rpm information like below and > > need to > > modify it accordingly: > > > > # yum info crash-gcore-command > > Loaded plugins: langpacks, product-id, search-disabled-repos, > > subscription-manager > > Available Packages > > Name: crash-gcore-command > > Arch: x86_64 > > Version : 1.3.1 > > Release : 0.el7 > > Size: 41 k > > Repo: rhel-7-server-rpms/7Server/x86_64 > > Summary : Gcore extension module for the crash utility > > URL : > > http://people.redhat.com/anderson/extensions/crash-gcore-command-1.3.1.tar.gz > > License : GPLv2 > > Description : Command for creating a core dump file of a user-space > > task that > > : was running in a kernel dumpfile. > > Yes, when the packages are updated, the URLs will have to be changed. During > the build > procedure, the package verification will fail if the upstream URL is defunct. > > > > > Also, when I want to release a new version of crash extnesion module, I > > send it to Hagio-san via > > this mailing list as in the past, and then Hagio-san modifies the "crash > > extension modules" page. > > Is this understanding correct? > > Yes, and then Kazu, Liang or Bhupesh will be able to update that page. > > > > > > I want to express my appreciation to all of you who have contributed > > > patches, both bug fixes and new features, and most importantly, to the > > > support from users who have kept the crash utility alive for over 20 years > > > now. It has been my great pleasure to have had the chance to work with > > > such an extraordinary international cast of characters. > > > > > > I will still be lurking as a regular subscriber to this list, at my > > > home address: ander...@prospeed.net > > > > > > It will be fun to watch what happens... > > > > > > Best wishes to all of you in these trying times, > > > > Thanks for your work on crash utility. This is essential for our daily > > support jobs. > > > > Personally, I met crash utility relatively early when I entered this field > > and have > > learnt a lot thorough using, reading and writing crash utility and lots of > > reviews > > by you this 10 years. > > I can't thank you enough Daisuke. Over the years you have been one of my most > dependable and valued contributors. Your finger prints are all over the crash > utility! > > Best Regards, > Dave > > > > > > > > Thanks. > > HATAYAMA, Daisuke > > > > > > > > > > > > -- > Crash-utility mailing list > Crash-utility@redhat.com > https://www.redhat.com/mailman/listinfo/crash-utility -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
- Original Message - > Dave, > > > Initially Kazuhito will primarily be handling upstream github duties, > > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > > RHEL maintenance. All three will be involved in the acceptance of > > patches posted on this mailing list. Please welcome them in their > > new roles; I am confident they will do a terrific job. > > Maybe, is it better to send patch set via github as PR from now on? I'm now > writing > zram patch set for x86-64 support. Hi Daisuke, Good question -- and one that I shall defer the answer to the new maintainers. Personally, I never accepted git pull requests because I always felt that it was more valuable to expose proposed patches to the larger audience that make up this mailing list. So when PRs came in, I coerced the submitter to use the list. > > > Since the https://people.redhat.com/anderson web page will be > > decommissioned after my departure, its contents have been moved > > to be co-located with the crash-utility github site: > > > > https://crash-utility.github.io > > Do you plan to set a redirection from the current page? Rpm packages for > crash's extension modules have URL in each rpm information like below and > need to > modify it accordingly: > > # yum info crash-gcore-command > Loaded plugins: langpacks, product-id, search-disabled-repos, > subscription-manager > Available Packages > Name: crash-gcore-command > Arch: x86_64 > Version : 1.3.1 > Release : 0.el7 > Size: 41 k > Repo: rhel-7-server-rpms/7Server/x86_64 > Summary : Gcore extension module for the crash utility > URL : > http://people.redhat.com/anderson/extensions/crash-gcore-command-1.3.1.tar.gz > License : GPLv2 > Description : Command for creating a core dump file of a user-space task > that > : was running in a kernel dumpfile. Yes, when the packages are updated, the URLs will have to be changed. During the build procedure, the package verification will fail if the upstream URL is defunct. > > Also, when I want to release a new version of crash extnesion module, I send > it to Hagio-san via > this mailing list as in the past, and then Hagio-san modifies the "crash > extension modules" page. > Is this understanding correct? Yes, and then Kazu, Liang or Bhupesh will be able to update that page. > > > I want to express my appreciation to all of you who have contributed > > patches, both bug fixes and new features, and most importantly, to the > > support from users who have kept the crash utility alive for over 20 years > > now. It has been my great pleasure to have had the chance to work with > > such an extraordinary international cast of characters. > > > > I will still be lurking as a regular subscriber to this list, at my > > home address: ander...@prospeed.net > > > > It will be fun to watch what happens... > > > > Best wishes to all of you in these trying times, > > Thanks for your work on crash utility. This is essential for our daily > support jobs. > > Personally, I met crash utility relatively early when I entered this field > and have > learnt a lot thorough using, reading and writing crash utility and lots of > reviews > by you this 10 years. I can't thank you enough Daisuke. Over the years you have been one of my most dependable and valued contributors. Your finger prints are all over the crash utility! Best Regards, Dave > > Thanks. > HATAYAMA, Daisuke > > > > > -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
Dave, > Initially Kazuhito will primarily be handling upstream github duties, > while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and > RHEL maintenance. All three will be involved in the acceptance of > patches posted on this mailing list. Please welcome them in their > new roles; I am confident they will do a terrific job. Maybe, is it better to send patch set via github as PR from now on? I'm now writing zram patch set for x86-64 support. > Since the https://people.redhat.com/anderson web page will be > decommissioned after my departure, its contents have been moved > to be co-located with the crash-utility github site: > > https://crash-utility.github.io Do you plan to set a redirection from the current page? Rpm packages for crash's extension modules have URL in each rpm information like below and need to modify it accordingly: # yum info crash-gcore-command Loaded plugins: langpacks, product-id, search-disabled-repos, subscription- : manager Available Packages Name: crash-gcore-command Arch: x86_64 Version : 1.3.1 Release : 0.el7 Size: 41 k Repo: rhel-7-server-rpms/7Server/x86_64 Summary : Gcore extension module for the crash utility URL : http://people.redhat.com/anderson/extensions/crash-gcore-command-1.3.1.tar.gz License : GPLv2 Description : Command for creating a core dump file of a user-space task that : was running in a kernel dumpfile. Also, when I want to release a new version of crash extnesion module, I send it to Hagio-san via this mailing list as in the past, and then Hagio-san modifies the "crash extension modules" page. Is this understanding correct? > I want to express my appreciation to all of you who have contributed > patches, both bug fixes and new features, and most importantly, to the > support from users who have kept the crash utility alive for over 20 years > now. It has been my great pleasure to have had the chance to work with > such an extraordinary international cast of characters. > > I will still be lurking as a regular subscriber to this list, at my > home address: ander...@prospeed.net > > It will be fun to watch what happens... > > Best wishes to all of you in these trying times, Thanks for your work on crash utility. This is essential for our daily support jobs. Personally, I met crash utility relatively early when I entered this field and have learnt a lot thorough using, reading and writing crash utility and lots of reviews by you this 10 years. Thanks. HATAYAMA, Daisuke -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
- Original Message - > On Mon, 4 May 2020 10:10:52 -0400 (EDT) > Dave Anderson wrote: > > > I'd like to take the opportunity to announce my retirement from > > Red Hat, and from the workforce in general. My last day at Red Hat > > will be May 29th, 2020. > > First, Dave, thank you very much for all the years maintaining this > extremely useful tool. You will be missed! > > > Accordingly, I will be relinquishing my role as maintainer of the > > crash utility. My replacement will be made up of three > > co-maintainers: > > > > Kazuhito Hagio k-hagio...@nec.com > > Lianbo Jiang liji...@redhat.com > > Bhupesh Sharma bhsha...@redhat.com > > Good luck to you. > > Just curious, is there some sort of hierarchy, or is this a virtual > team of people with equal rights and duties? They will have equal rights. But duty-wise, as I indicated, Kazu will handle the upstream github chores, while Lianbo and Bhupesh will take care of Fedora, CentOS stream and RHEL maintenance. But with that being said, Kazu will rely upon Lianbo and Bhupesh for multiple-architecture access at Red Hat that he does not have available at NEC. And while it's still under discussion, they have so far agreed that patches posted to the mailing list will require at least 2 ACKs from the 3 of them. Thanks, Dave > > Petr Tesarik > SUSE HW Enablement Team > -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
Re: [Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
On Mon, 4 May 2020 10:10:52 -0400 (EDT) Dave Anderson wrote: > I'd like to take the opportunity to announce my retirement from > Red Hat, and from the workforce in general. My last day at Red Hat > will be May 29th, 2020. First, Dave, thank you very much for all the years maintaining this extremely useful tool. You will be missed! > Accordingly, I will be relinquishing my role as maintainer of the > crash utility. My replacement will be made up of three > co-maintainers: > > Kazuhito Hagio k-hagio...@nec.com > Lianbo Jiang liji...@redhat.com > Bhupesh Sharma bhsha...@redhat.com Good luck to you. Just curious, is there some sort of hierarchy, or is this a virtual team of people with equal rights and duties? Petr Tesarik SUSE HW Enablement Team pgpnH1plABbPe.pgp Description: Digitální podpis OpenPGP -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
[Crash-utility] [ANNOUNCE] My retirement, and crash utility maintainership changes
I'd like to take the opportunity to announce my retirement from Red Hat, and from the workforce in general. My last day at Red Hat will be May 29th, 2020. Accordingly, I will be relinquishing my role as maintainer of the crash utility. My replacement will be made up of three co-maintainers: Kazuhito Hagio k-hagio...@nec.com Lianbo Jiang liji...@redhat.com Bhupesh Sharma bhsha...@redhat.com As you may be aware, Kazuhito will be performing double-duty, as he is also the upstream maintainer of the makedumpfile facility; he has been a significant contributor to the crash utility. Lianbo and Bhupesh have both been working extensively in the kexec/kdump area, both in the kernel and the user-space utilities. Initially Kazuhito will primarily be handling upstream github duties, while Lianbo and Bhupesh will be handling Fedora, CentOS stream, and RHEL maintenance. All three will be involved in the acceptance of patches posted on this mailing list. Please welcome them in their new roles; I am confident they will do a terrific job. Since the https://people.redhat.com/anderson web page will be decommissioned after my departure, its contents have been moved to be co-located with the crash-utility github site: https://crash-utility.github.io I want to express my appreciation to all of you who have contributed patches, both bug fixes and new features, and most importantly, to the support from users who have kept the crash utility alive for over 20 years now. It has been my great pleasure to have had the chance to work with such an extraordinary international cast of characters. I will still be lurking as a regular subscriber to this list, at my home address: ander...@prospeed.net It will be fun to watch what happens... Best wishes to all of you in these trying times, Dave Anderson -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
