Re: Patch reason tracking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2013-11-18 at 21:40 -0500, Josh Boyer wrote:
> Hi All,
> 
> Every month I'm trying to publish a Fedora Kernel patch report that
> lists all of our patches and why we are carrying them.  Thankfully,
> the past couple of times I've done this it's been pretty clear that
> for the most part we're just carrying fixes queued up to head to Linus
> soon.
> 
> However, it also means I have to track down the status of that patch
> every month.  I've been trying to keep PatchList.txt up to date, but
> that isn't scaling very well as it's easy for people to forget to add
> patches to it or remove them when we drop the patch.  To help this
> tracking, I'd like to push the status information into each patch
> itself.  What I propose is basically to fields at the top of each
> patch:
> 
> Bugzilla:
> Upstream-status:
> 
> The first is fairly self-evident.  It just list the Red Hat Bugzilla
> number associated with the patch.  If there isn't one, just put N/A.

Only question I have is why/whether this needs to be rhbz, or if we
could just do arbitrary bz urls.  I don't really mind either way though.

- ajax

_______________________________________________
kernel mailing list
kernel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kernel





[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux