Module: tools
Branch: master
Commit: bc7d2a84263d536c8c0ba0d6f3c4580ff837c5aa
URL: http://source.winehq.org/git/tools.git/?a=commit;h=bc7d2a84263d536c8c0ba0d6…
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Nov 10 16:38:34 2017 +0100
testbot: Update documentation to point to wine-devel instead of wine-patches.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
---
testbot/README | 2 +-
testbot/bin/WinePatchesMLSubmit.pl | 2 +-
testbot/doc/INSTALL.txt | 11 +++++------
testbot/lib/WineTestBot/Config.pm | 2 +-
4 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/testbot/README b/testbot/README
index 3977c5d..8475abe 100644
--- a/testbot/README
+++ b/testbot/README
@@ -21,7 +21,7 @@ Windows machines. There are three ways this can happen:
* Registered users can submit patches and binaries using the web site
and have them run on the set of Windows machines of their choosing.
-* Conformance test patches sent to the wine-patches mailing list are
+* Conformance test patches sent to the wine-devel mailing list are
run on the default set of Windows machines. Any failure is reported
to the patch author and to the wine-devel mailing list.
diff --git a/testbot/bin/WinePatchesMLSubmit.pl b/testbot/bin/WinePatchesMLSubmit.pl
index 6dc39e8..65fe848 100755
--- a/testbot/bin/WinePatchesMLSubmit.pl
+++ b/testbot/bin/WinePatchesMLSubmit.pl
@@ -1,7 +1,7 @@
#!/usr/bin/perl -Tw
# -*- Mode: Perl; perl-indent-level: 2; indent-tabs-mode: nil -*-
#
-# This script expects to receive a wine-patches email on stdin and submits it
+# This script expects to receive a wine-devel email on stdin and submits it
# to WineTestBot for testing. It is meant to be called from a tool such as
# procmail.
#
diff --git a/testbot/doc/INSTALL.txt b/testbot/doc/INSTALL.txt
index 0b95656..9947150 100644
--- a/testbot/doc/INSTALL.txt
+++ b/testbot/doc/INSTALL.txt
@@ -89,17 +89,16 @@ Setup for Winetest updates:
*/10 * * * * $HOME/tools/testbot/bin/CheckForWinetestUpdate.pl 32
*/10 * * * * $HOME/tools/testbot/bin/CheckForWinetestUpdate.pl 64
-Setup for wine-patches:
+Setup for wine-devel:
- A proper WineTestBot system should integrate with Wine's patches site.
- An alternative is to interface directly with wine-patches as described in
+ An alternative is to interface directly with wine-devel as described in
this section.
- Arrange for the WinePatchesMLSubmit.pl script to be fed the
- wine-patches emails. One way to do so would be to subscribe the
- winehq user to the wine-patches mailing list and to then add the
+ wine-devel emails. One way to do so would be to subscribe the
+ winehq user to the wine-devel mailing list and to then add the
following lines to the .procmailrc file:
:0c:
- * ^List-Id: Wine Patch Submissions
- * ^TO wine-patches
+ * ^List-Id:.*wine-devel\.winehq\.org
| $HOME/tools/testbot/bin/WinePatchesMLSubmit.pl
- Or if you have a set of patches to test in the mbox format you can
test with:
diff --git a/testbot/lib/WineTestBot/Config.pm b/testbot/lib/WineTestBot/Config.pm
index 4f38633..b0492a3 100644
--- a/testbot/lib/WineTestBot/Config.pm
+++ b/testbot/lib/WineTestBot/Config.pm
@@ -96,7 +96,7 @@ $BuildTimeout = 5 * 60;
$ReconfigTimeout = 45 * 60;
$ProjectName = "Wine";
-$PatchesMailingList = "wine-patches";
+$PatchesMailingList = "wine-devel";
$LDAPServer = undef;
$LDAPBindDN = undef;
Module: tools
Branch: master
Commit: 2ac3b11f32c5db5128d893e907bb424a2fc29015
URL: http://source.winehq.org/git/tools.git/?a=commit;h=2ac3b11f32c5db5128d893e9…
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Nov 10 16:38:21 2017 +0100
patches: Update documentation to point to wine-devel instead of wine-patches.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
---
patches/doc/INSTALL.txt | 13 +++++--------
patches/expire | 2 +-
patches/filter | 2 +-
3 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/patches/doc/INSTALL.txt b/patches/doc/INSTALL.txt
index c1570ac..e1ef2b8 100644
--- a/patches/doc/INSTALL.txt
+++ b/patches/doc/INSTALL.txt
@@ -37,14 +37,13 @@ Apache setup:
- Create the $HOME/opt/source/patches directory and copy patches.css there:
mkdir $HOME/opt/source/patches
cp patches.css $HOME/opt/source/patches
-- Create the $HOME/patches and $HOME/patches/OLD directories where the patch
- data will live:
- mkdir -p $HOME/patches/OLD
-- Arrange for the filter script to be fed the wine-patches emails. One way to
- do so would be to subscribe the winehq user to the wine-patches mailing list
+- Create the $HOME/patches directory where the patch data will live:
+ mkdir -p $HOME/patches
+- Arrange for the filter script to be fed the wine-devel emails. One way to
+ do so would be to subscribe the winehq user to the wine-devel mailing list
and to then add the following lines to the .procmailrc file:
:0
- * ^List-Id: Wine Patch Submissions
+ * ^List-Id:.*wine-devel\.winehq\.org
{
:0 hbfw
| $HOME/tools/patches/filter
@@ -55,8 +54,6 @@ Apache setup:
formail -ds procmail <mbox-file
- Run update regularly to update the website:
*/5 * * * * $HOME/tools/patches/update
-- Run expire regularly to delete old patches:
- 0 0 * * * $HOME/tools/patches/expire -v $HOME/patches
For integration with the WineTestBot, see the corresponding section in the
WineTestBot documentation.
diff --git a/patches/expire b/patches/expire
index 305e7e5..513a5b1 100755
--- a/patches/expire
+++ b/patches/expire
@@ -345,7 +345,7 @@ asked to review the following Wine $patch_str:
$patch_urls
If you think that a patch is correct and can be committed, please send
-a mail to wine-patches with your Signed-off-by header, as a reply to
+a mail to wine-devel with your Signed-off-by header, as a reply to
the original patch email.
If you find some issues in a patch, please send a mail to the patch
diff --git a/patches/filter b/patches/filter
index 62e2a0d..7074d96 100755
--- a/patches/filter
+++ b/patches/filter
@@ -1,6 +1,6 @@
#!/usr/bin/perl -w
#
-# Reformat a wine-patches email so it can be put in a file that the patches
+# Reformat a wine-devel email so it can be put in a file that the patches
# site can link to. In particular this means only keeping the relevant
# header fields and decoding / decompressing the patch.
#
Module: tools
Branch: master
Commit: d84c6603d7bf9db05318d2c17db6ff9529cb92f8
URL: http://source.winehq.org/git/tools.git/?a=commit;h=d84c6603d7bf9db05318d2c1…
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Nov 8 21:08:25 2017 +0100
patches: Remove some no longer used patch states.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
---
patches/expire | 15 ++-------------
patches/patches.css | 2 --
patches/update | 5 -----
3 files changed, 2 insertions(+), 20 deletions(-)
diff --git a/patches/expire b/patches/expire
index 4dd8a1a..305e7e5 100755
--- a/patches/expire
+++ b/patches/expire
@@ -24,7 +24,6 @@
my %status_expiry =
(
"nil" => 30,
- "pending" => 30,
"assigned" => 30,
"applied" => 30,
"committed" => 1,
@@ -35,12 +34,11 @@ my %status_expiry =
"formatting" => 7,
"other" => 7,
"nopatch" => 3,
- "reply" => 7,
+ "reply" => 1,
"rejected" => 7,
"split" => 7,
"depend" => 7,
"sequence" => 7,
- "signoff" => 1,
"superseded" => 1,
"testcase" => 7,
"testfail" => 7,
@@ -49,7 +47,6 @@ my %status_expiry =
my %status_descr =
(
"nil" => "New",
- "pending" => "Pending",
"assigned" => "Assigned",
"applied" => "Applied",
"committed" => "Committed",
@@ -65,7 +62,6 @@ my %status_descr =
"split" => "Needs splitting",
"depend" => "Dependency",
"sequence" => "Bad sequence",
- "signoff" => "Sign-off",
"superseded" => "Superseded",
"testcase" => "Needs tests",
"testfail" => "Test failure",
@@ -73,12 +69,6 @@ my %status_descr =
my %status_explanation =
(
- "pending" =>
-"This means that the patch is not necessarily wrong, but its
-correctness is not obvious. You should either write a test case
-demonstrating that it is correct, try to fix the problem in a more
-straightforward way, or better explain why you are doing things this
-way.",
"assigned" =>
"This means that the patch has been assigned to a reviewer. If the
reviewer signs off on the patch, it will be committed, otherwise
@@ -142,7 +132,6 @@ to enable the Testbot to figure it out.",
the patch is correct.",
# No notifications are sent for the following:
# "nil"
-# "signoff"
# "reply"
# "superseded"
# "testfail"
@@ -213,7 +202,7 @@ sub get_patch_state($)
{
$status = <STATUS>;
chomp $status;
- $mtime = (stat STATUS)[9] unless ($status eq "nil" || $status eq "pending");
+ $mtime = (stat STATUS)[9] unless $status eq "nil";
close STATUS;
}
$mtime ||= (stat "$dir/$file")[9];
diff --git a/patches/patches.css b/patches/patches.css
index f7bb560..24e8f37 100644
--- a/patches/patches.css
+++ b/patches/patches.css
@@ -153,7 +153,6 @@ tr.odd { background-color: #f8e8e8; }
.id :hover, .sha1 :hover, .subject :hover { color: #FF6666; text-decoration: underline; }
.nil, .nil :link, .nil :visited { color: blue; font-weight: bold; }
-.pending, .pending :link, .pending :visited { color: blue; }
.assigned, .assigned :link, .assigned :visited { color: blue; }
.committed, .committed :link, .committed :visited { color: green; }
.depend, .depend :link, .depend :visited { color: #e08000; }
@@ -161,7 +160,6 @@ tr.odd { background-color: #f8e8e8; }
.sequence, .sequence :link, .sequence :visited { color: #e08000; }
.deferred, .deferred :link, .deferred :visited { color: #e08000; }
.testcase, .testcase :link, .testcase :visited { color: #e08000; }
-.signoff, .signoff :link, .signoff :visited { color: #e08000; }
.reply, .reply :link, .reply :visited { color: #e08000; }
.other, .other :link, .other :visited { color: #e08000; }
.applyfail, .applyfail :link, .applyfail :visited { color: red; }
diff --git a/patches/update b/patches/update
index ca4d2e5..5e82927 100755
--- a/patches/update
+++ b/patches/update
@@ -24,7 +24,6 @@ use CGI qw(:standard);
my %status_descr =
(
"nil" => "New",
- "pending" => "Pending",
"assigned" => "Assigned",
"applied" => "Applied",
"committed" => "Committed",
@@ -42,14 +41,12 @@ my %status_descr =
"sequence" => "Bad sequence",
"testcase" => "Needs tests",
"testfail" => "Test failure",
- "signoff" => "Sign-off",
"reply" => "Reply",
);
my @legend =
(
[ "nil", "<ul><li>Patch not even looked at yet, there's still hope...</li></ul>" ],
- [ "pending", "<ul><li>The patch is not obviously correct at first glance. Making a more convincing argument, preferably in the form of a test case, may help.</li></ul>" ],
[ "assigned", "<ul><li>Waiting for sign-off or feedback from the assigned reviewer. If you don't hear anything after a couple of weeks, please resend the patch.</li></ul>" ],
[ "committed", "<ul><li>You have done everything right; congratulations!</li>" .
"<li>You screwed up but AJ missed it, send a fix before someone notices ;-)</li></ul>" ],
@@ -59,8 +56,6 @@ my @legend =
"<li>Someone else fixed the problem already.</li></ul>" ],
[ "testcase", "<ul><li>You need to write some test cases demonstrating that the patch is correct.</li></ul>" ],
[ "deferred", "<ul><li>The patch is deferred because of code freeze for an upcoming release. Either resend after the release, make the patch less intrusive, or make a convincing argument that it needs to be included in the release.</li></ul>" ],
- [ "signoff", "<ul><li>This is a Signed-off-by reply to another patch.</li></ul>" ],
- [ "reply", "<ul><li>The mail is a reply to another patch.</li></ul>" ],
[ "other", "<ul><li>The patch belongs to another WineHQ project (website, appdb, etc.) and will be applied by the respective maintainer.</li></ul>" ],
[ "applyfail", "<ul><li>The patch got mangled in transit.</li>" .
"<li>It's not relative to the latest git.</li>" .