On Mon, Jun 22, 2020 at 03:54:21PM +0200, Vít Ondruch wrote: > > Dne 20. 06. 20 v 19:34 Kevin Fenzi napsal(a): > > On Fri, Jun 19, 2020 at 11:07:59AM +0200, Vít Ondruch wrote: > >> Dne 18. 06. 20 v 19:48 Kevin Fenzi napsal(a): > >>> On Thu, Jun 18, 2020 at 10:12:11AM +0200, Vít Ondruch wrote: > >>>> Dne 17. 06. 20 v 19:54 Kevin Fenzi napsal(a): > >>>>> On Tue, Jun 16, 2020 at 09:23:38AM +0200, Vít Ondruch wrote: > >>>>> > >>>>> Theres not a seperate one for epel, but it might be possible to make > >>>>> one looking at bugzilla overrides. > >>>> Just to give you a bit of context, this alias would be useful when > >>>> introducing new package into RHEL, where the package is already present > >>>> in EPEL and therefore have to be removed. So it would help with a way to > >>>> contact the relevant people without the need of gathering their emails. > >>> Yeah, +1. This would be a great use for that alias. > >> > >> Should I open a ticket? Is this realistic any time soon? > > For documenting the aliases? Well, you can edit the wiki... or did you > > want a better place for it, like in docs? > > > > Or did you mean getting RHEL maintainers to mail it when introducing new > > packages to RHEL? Thats beyond our scope here, and would have to be some > > internal process. > > > > Sorry for getting lost you here. I was still talking about the EPEL > email alias. So is the EPEL email alias thing which could be implemented > soon so is it worth of opening ticket? Ah, I see. Yes, please do file a ticket and we can try and implement it. ;) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
