On Fri, Nov 25, 2016 at 05:54:41PM +1300, Kent Fredric wrote: > On Fri, 25 Nov 2016 06:41:20 +1100 > Michael Palimaka <kensing...@gentoo.org> wrote: > > > Example atom list from a bug with amd64, arm, and x86 in CC: > > > > =app-foo/bar-1.2.3 # will be stabilised on amd64, arm, and x86 > > =app-foo/baz-2.3.4 amd64 x86 # will be stabilised on only amd64 and x86 > > I was doing this in the past, but there's a reason I stopped: > > Bugzilla-enforced wordwrap ( at least, this is very strict on the > bugzilla-email relay ) > > > =app-foo/bar-1.2.3 # will be stabilised on amd64, arm, and x86 > > Could become more like > > > =app-foo/bar-1.2.3 # will be stabilised on amd64, > > arm, and x86
One way would be to use a plain text attachment with a standardized filename. If there are updates to the list then the new should obsolete the old and the script can pull non-obsoleted ones. The problem then is how do you search for them properly? put them all in the title anyway? then its duplicated. When i do big lists of packages the title is eg "XFCE Stabilization for Nov 2016" which is not duplicated and okay. For single packages the title is just "cat/pkg-1.2.3 stablereq" so then we duplicate anyway? -- Jason > A literal example of an email I received for a bug I filed ( via an alias ) > is attached. > > The example I give did not render poorly on bugzilla > ( https://bugs.gentoo.org/show_bug.cgi?id=599550 ), but I suspect people > who do AT probably prefer their notification emails about needed AT not > to be useless. >
