third_party/libxslt/HACKING - Issue 1193533007: Upgrade to libxml 2.9.2 and libxslt 1.1.28

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: third_party/libxslt/HACKING

Issue 1193533007: Upgrade to libxml 2.9.2 and libxslt 1.1.28 (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: remove suppressions, have landed in blink now Created 5 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 Rules for commits on the libxslt module

	2 =======================================

	3

	4 If what you are fixing is a compilation issue either at compile

	5 time or linking time on one of the main Linux platforms, then feel free

	6 to patch first and send mail afterward, as long as it's a 'small fix'.

	7

	8 Otherwise, only Bjorn Reese (breese@users.sourceforge.net),

	9 "William M. Brack" <wbrack@mmm.com.hk>, Igor Zlatkovic

	10 <igor@zlatkovic.com> and me (veillard@redhat.com)

	11 should commit there. John Fleck also have commit rights for the doc

	12 subdir. Send a mail and if it's a bug issue, provide a test case and

	13 register it at bugzilla.gnome.org in the libxslt module.

	14 I check both my mail and the bug database on a very regular basis.

	15 if you don't get an answer within a week (which is highly unprobable)

	16 then commit your changes. This simply mean that I am on holliday or

	17 on the road and the other maintainers are busy too.

	18

	19 thanks in advance for following the rule,

	20

	21 Daniel

	22

OLD	NEW