Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
67be57eb
L
libvirt
项目概览
openeuler
/
libvirt
通知
3
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
L
libvirt
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
67be57eb
编写于
10月 21, 2014
作者:
M
Martin Kletzander
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
docs: Mention repository locations in contributor guidelines
Signed-off-by:
N
Martin Kletzander
<
mkletzan@redhat.com
>
上级
9661ac2f
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
16 addition
and
7 deletion
+16
-7
HACKING
HACKING
+11
-7
docs/hacking.html.in
docs/hacking.html.in
+5
-0
未找到文件。
HACKING
浏览文件 @
67be57eb
...
...
@@ -14,7 +14,11 @@ General tips for contributing patches
(1) Discuss any large changes on the mailing list first. Post patches early and
listen to feedback.
(2) Post patches in unified diff format, with git rename detection enabled. You
(2) Official upstream repository is kept in git ("git://libvirt.org/libvirt.git")
and is browsable along with other libvirt-related repositories (e.g.
libvirt-python) online <http://libvirt.org>.
(3) Post patches in unified diff format, with git rename detection enabled. You
need a one-time setup of:
git config diff.renames true
...
...
@@ -66,7 +70,7 @@ though).
(
3
) In your commit message, make the summary line reasonably short (60 characters
(
4
) In your commit message, make the summary line reasonably short (60 characters
is typical), followed by a blank line, followed by any longer description of
why your patch makes sense. If the patch fixes a regression, and you know what
commit introduced the problem, mentioning that is useful. If the patch
...
...
@@ -78,7 +82,7 @@ is up to you if you want to include or omit them in the commit message.
(
4
) Split large changes into a series of smaller patches, self-contained if
(
5
) Split large changes into a series of smaller patches, self-contained if
possible, with an explanation of each patch and an explanation of how the
sequence of patches fits together. Moreover, please keep in mind that it's
required to be able to compile cleanly (*including* "make check" and "make
...
...
@@ -89,10 +93,10 @@ things).
(
5
) Make sure your patches apply against libvirt GIT. Developers only follow GIT
(
6
) Make sure your patches apply against libvirt GIT. Developers only follow GIT
and don't care much about released versions.
(
6
) Run the automated tests on your code before submitting any changes. In
(
7
) Run the automated tests on your code before submitting any changes. In
particular, configure with compile warnings set to -Werror. This is done
automatically for a git checkout; from a tarball, use:
...
...
@@ -138,7 +142,7 @@ various tests under gdb or Valgrind.
(
7
) The Valgrind test should produce similar output to "make check". If the output
(
8
) The Valgrind test should produce similar output to "make check". If the output
has traces within libvirt API's, then investigation is required in order to
determine the cause of the issue. Output such as the following indicates some
sort of leak:
...
...
@@ -214,7 +218,7 @@ to "tests/.valgrind.supp" in order to suppress the warning:
(
8
) Update tests and/or documentation, particularly if you are adding a new
(
9
) Update tests and/or documentation, particularly if you are adding a new
feature or changing the output of a program.
...
...
docs/hacking.html.in
浏览文件 @
67be57eb
...
...
@@ -11,6 +11,11 @@
<li>
Discuss any large changes on the mailing list first. Post patches
early and listen to feedback.
</li>
<li>
Official upstream repository is kept in git
(
<code>
git://libvirt.org/libvirt.git
</code>
) and is browsable
along with other libvirt-related repositories
(e.g. libvirt-python)
<a
href=
"http://libvirt.org"
>
online
</a>
.
</li>
<li><p>
Post patches in unified diff format, with git rename
detection enabled. You need a one-time setup of:
</p>
<pre>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录