提交 d39e3b71 编写于 作者: A Andrea Bolognani

HACKING: Regenerate

When updating the source file in commit bd4f4d16, I forgot
that we also store the generated plain text version in git and
didn't regenerate it.

I also missed one spot that required an additional <p> tag, so
fix both mistakes in one go.
上级 f0af48f0
...@@ -14,15 +14,21 @@ General tips for contributing patches ...@@ -14,15 +14,21 @@ General tips for contributing patches
(1) Discuss any large changes on the mailing list first. Post patches early and (1) Discuss any large changes on the mailing list first. Post patches early and
listen to feedback. listen to feedback.
(2) Official upstream repository is kept in git ("git://libvirt.org/libvirt.git") (2) Official upstream repository is kept in git ("git://libvirt.org/libvirt.git")
and is browsable along with other libvirt-related repositories (e.g. and is browsable along with other libvirt-related repositories (e.g.
libvirt-python) online <http://libvirt.org/git/>. libvirt-python) online <http://libvirt.org/git/>.
(3) Patches to translations are maintained via the zanata project (3) Patches to translations are maintained via the zanata project
<https://fedora.zanata.org/>. If you want to fix a translation in a .po file, <https://fedora.zanata.org/>. If you want to fix a translation in a .po file,
join the appropriate language team. The libvirt release process automatically join the appropriate language team. The libvirt release process automatically
pulls the latest version of each translation file from zanata. pulls the latest version of each translation file from zanata.
(4) Post patches using "git send-email", with git rename detection enabled. You (4) Post patches using "git send-email", with git rename detection enabled. You
need a one-time setup of: need a one-time setup of:
...@@ -93,6 +99,8 @@ things). ...@@ -93,6 +99,8 @@ things).
(7) Make sure your patches apply against libvirt GIT. Developers only follow GIT (7) Make sure your patches apply against libvirt GIT. Developers only follow GIT
and don't care much about released versions. and don't care much about released versions.
(8) Run the automated tests on your code before submitting any changes. In (8) Run the automated tests on your code before submitting any changes. In
particular, configure with compile warnings set to -Werror. This is done particular, configure with compile warnings set to -Werror. This is done
automatically for a git checkout; from a tarball, use: automatically for a git checkout; from a tarball, use:
...@@ -238,6 +246,8 @@ feature or changing the output of a program. ...@@ -238,6 +246,8 @@ feature or changing the output of a program.
There is more on this subject, including lots of links to background reading There is more on this subject, including lots of links to background reading
on the subject, on Richard Jones' guide to working with open source projects on the subject, on Richard Jones' guide to working with open source projects
<http://people.redhat.com/rjones/how-to-supply-code-to-open-source-projects/>. <http://people.redhat.com/rjones/how-to-supply-code-to-open-source-projects/>.
......
...@@ -289,8 +289,11 @@ ...@@ -289,8 +289,11 @@
} }
</pre> </pre>
</li> </li>
<li>Update tests and/or documentation, particularly if you are adding
a new feature or changing the output of a program.</li> <li>
<p>Update tests and/or documentation, particularly if you are adding
a new feature or changing the output of a program.</p>
</li>
</ol> </ol>
<p> <p>
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册