WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
65714
Update the contributors page to recommend webkit-patch instead of many manual steps
https://bugs.webkit.org/show_bug.cgi?id=65714
Summary
Update the contributors page to recommend webkit-patch instead of many manual...
Nico Weber
Reported
2011-08-04 13:19:56 PDT
Update the contributors page to recommend webkit-patch instead of many manual steps
Attachments
Patch
(7.66 KB, patch)
2011-08-04 13:23 PDT
,
Nico Weber
no flags
Details
Formatted Diff
Diff
Patch
(7.65 KB, patch)
2011-08-04 14:40 PDT
,
Nico Weber
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Nico Weber
Comment 1
2011-08-04 13:23:00 PDT
Created
attachment 102967
[details]
Patch
Adam Barth
Comment 2
2011-08-04 13:28:06 PDT
Comment on
attachment 102967
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=102967&action=review
> Websites/webkit.org/coding/contributing.html:125 > +<p>The easiest way to create a patch is to run > +<code>Tools/Scripts/webkit-patch upload</code>. This will upload your current > +Subversion diff (or Git diff if you
Should we say that you can supply the bug number if the bug already exists?
> Websites/webkit.org/coding/contributing.html:137 > +<p>The "No new tests. (OOPS!)" line appears if <code>prepare-ChangeLog</code> did not detect the addition of test cases. If your patch does not require test cases (or test cases are not possible), you should include a line stating such. Otherwise all changes require test cases which should be mentioned in the ChangeLog.</p>
Rather than saying "you should include a line stating such" maybe we should say that you should replace the OOPS line with an explanation, etc. It's a common error to leave in the "No new tests" OOPS line, which prevents the patch from landing.
Nico Weber
Comment 3
2011-08-04 14:39:56 PDT
> Should we say that you can supply the bug number if the bug already exists?
webkit-patch prints "Enter title or issue number" or something like that, so I don't think this is necessary.
> > > Websites/webkit.org/coding/contributing.html:137 > > +<p>The "No new tests. (OOPS!)" line appears if <code>prepare-ChangeLog</code> did not detect the addition of test cases. If your patch does not require test cases (or test cases are not possible), you should include a line stating such. Otherwise all changes require test cases which should be mentioned in the ChangeLog.</p> > > Rather than saying "you should include a line stating such" maybe we should say that you should replace the OOPS line with an explanation, etc. It's a common error to leave in the "No new tests" OOPS line, which prevents the patch from landing.
Done.
Nico Weber
Comment 4
2011-08-04 14:40:01 PDT
Created
attachment 102983
[details]
Patch
Adam Barth
Comment 5
2011-08-04 14:42:43 PDT
(In reply to
comment #3
)
> > Should we say that you can supply the bug number if the bug already exists? > > webkit-patch prints "Enter title or issue number" or something like that, so I don't think this is necessary.
Oh, I totally forgot about that feature.
Adam Barth
Comment 6
2011-08-04 14:44:17 PDT
Comment on
attachment 102983
[details]
Patch Ok. I'll be on the lookout for new contributors having trouble with webkit-patch. Thanks for updating the docs.
WebKit Review Bot
Comment 7
2011-08-04 15:42:06 PDT
Comment on
attachment 102983
[details]
Patch Clearing flags on attachment: 102983 Committed
r92421
: <
http://trac.webkit.org/changeset/92421
>
WebKit Review Bot
Comment 8
2011-08-04 15:42:10 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug