Add a README file which explains what's the process for kexec-tools patch inclusion and where one should post patches for review. This should help with removing some confusion.
Signed-off-by: Vivek Goyal vgoyal@redhat.com --- README | 12 ++++++++++++ 1 file changed, 12 insertions(+)
Index: kexec-tools-fedora/README =================================================================== --- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ kexec-tools-fedora/README 2014-03-27 14:44:38.210938613 -0400 @@ -0,0 +1,12 @@ +Adding a patch to kexec-tools +============================= +There is a mailing list kexec@lists.fedoraproject.org where all the dicussion +related to fedora kexec-tools happen. All the patches are posted there for +inclusion and committed to kexec-tools after review. + +So if you want your patches to be included in fedora kexec-tools package, +post these to kexec@lists.fedoraproject.org. + +One can subscribe to list and browse through archives here. + +https://admin.fedoraproject.org/mailman/listinfo/kexec
On 03/27/14 at 02:45pm, Vivek Goyal wrote:
Add a README file which explains what's the process for kexec-tools patch inclusion and where one should post patches for review. This should help with removing some confusion.
Signed-off-by: Vivek Goyal vgoyal@redhat.com
Ack. Thanks Vivek. Do you think some comment is necessary in spec file?
README | 12 ++++++++++++ 1 file changed, 12 insertions(+)
Index: kexec-tools-fedora/README
--- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ kexec-tools-fedora/README 2014-03-27 14:44:38.210938613 -0400 @@ -0,0 +1,12 @@ +Adding a patch to kexec-tools +============================= +There is a mailing list kexec@lists.fedoraproject.org where all the dicussion +related to fedora kexec-tools happen. All the patches are posted there for +inclusion and committed to kexec-tools after review.
+So if you want your patches to be included in fedora kexec-tools package, +post these to kexec@lists.fedoraproject.org.
+One can subscribe to list and browse through archives here.
+https://admin.fedoraproject.org/mailman/listinfo/kexec _______________________________________________ kexec mailing list kexec@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/kexec
Ack
As Dave mentioned, do we need to install this file to system, or just put it in fedora git repo, let people know how to post patch only?
Thanks Baoquan
On 03/27/14 at 02:45pm, Vivek Goyal wrote:
Add a README file which explains what's the process for kexec-tools patch inclusion and where one should post patches for review. This should help with removing some confusion.
Signed-off-by: Vivek Goyal vgoyal@redhat.com
README | 12 ++++++++++++ 1 file changed, 12 insertions(+)
Index: kexec-tools-fedora/README
--- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ kexec-tools-fedora/README 2014-03-27 14:44:38.210938613 -0400 @@ -0,0 +1,12 @@ +Adding a patch to kexec-tools +============================= +There is a mailing list kexec@lists.fedoraproject.org where all the dicussion +related to fedora kexec-tools happen. All the patches are posted there for +inclusion and committed to kexec-tools after review.
+So if you want your patches to be included in fedora kexec-tools package, +post these to kexec@lists.fedoraproject.org.
+One can subscribe to list and browse through archives here.
+https://admin.fedoraproject.org/mailman/listinfo/kexec _______________________________________________ kexec mailing list kexec@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/kexec
On 04/01/14 at 10:04am, Baoquan He wrote:
Ack
As Dave mentioned, do we need to install this file to system, or just put it in fedora git repo, let people know how to post patch only?
I think put it in git is good enough. We don't really need such file in our rpm.
Thanks WANG Chao
On 04/01/14 at 10:04am, Baoquan He wrote:
Ack
As Dave mentioned, do we need to install this file to system, or just put it in fedora git repo, let people know how to post patch only?
I think put it in git repo is enough. What I wonder is if we should add comments to the head of spec file since most of the random commits from other maintainer is for rpm spec modifications.
Thanks Dave
On Tue, Apr 01, 2014 at 06:05:03PM +0800, Dave Young wrote:
On 04/01/14 at 10:04am, Baoquan He wrote:
Ack
As Dave mentioned, do we need to install this file to system, or just put it in fedora git repo, let people know how to post patch only?
I think put it in git repo is enough. What I wonder is if we should add comments to the head of spec file since most of the random commits from other maintainer is for rpm spec modifications.
I agree that keep it in git only at this momemnt. We have other howto files which get installed.
I am not too keen on putting something in spec file. If people start not noticing README file, then we can think of putting couple of lines in spec file too.
Thanks Vivek
On 03/27/14 at 02:45pm, Vivek Goyal wrote:
Add a README file which explains what's the process for kexec-tools patch inclusion and where one should post patches for review. This should help with removing some confusion.
Signed-off-by: Vivek Goyal vgoyal@redhat.com
This looks good to me. Thanks.
Acked-by: WANG Chao chaowang@redhat.com
README | 12 ++++++++++++ 1 file changed, 12 insertions(+)
Index: kexec-tools-fedora/README
--- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ kexec-tools-fedora/README 2014-03-27 14:44:38.210938613 -0400 @@ -0,0 +1,12 @@ +Adding a patch to kexec-tools +============================= +There is a mailing list kexec@lists.fedoraproject.org where all the dicussion +related to fedora kexec-tools happen. All the patches are posted there for +inclusion and committed to kexec-tools after review.
+So if you want your patches to be included in fedora kexec-tools package, +post these to kexec@lists.fedoraproject.org.
+One can subscribe to list and browse through archives here.
+https://admin.fedoraproject.org/mailman/listinfo/kexec _______________________________________________ kexec mailing list kexec@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/kexec