Team,
Patches are sent to the list for review from all branches of anaconda.
I'd like to propose a simple improvement to help us identify which
branch a patch is for:
1) If your patch is for rawhide, do nothing new. It is assumed all
patches without a branch identification are for rawhide.
2) If your patch is for a branch, use the --subject and/or the --compose
switch on 'git send-email' to add 'XXX-branch' to the beginning of your
subject line.
If anyone knows a magical git command that will do this automatically,
please speak up.
--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
