Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
4a9ebf7d
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看板
提交
4a9ebf7d
编写于
6月 02, 2008
作者:
R
Richard W.M. Jones
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
General tips for contributing patches
* HACKING: Added section "general tips for contributing patches" to this file.
上级
f855e91f
变更
2
显示空白变更内容
内联
并排
Showing
2 changed file
with
47 addition
and
1 deletion
+47
-1
ChangeLog
ChangeLog
+6
-0
HACKING
HACKING
+41
-1
未找到文件。
ChangeLog
浏览文件 @
4a9ebf7d
Mon Jun 2 12:52:00 BST 2008 Richard W.M. Jones <rjones@redhat.com>
General tips for contributing patches
* HACKING: Added section "general tips for contributing patches"
to this file.
Thu May 29 16:43:00 EST 2008 Daniel P. Berrange <berrange@redhat.com>
Thu May 29 16:43:00 EST 2008 Daniel P. Berrange <berrange@redhat.com>
* autobuild.sh: Only run converage tests if lcov is installed
* autobuild.sh: Only run converage tests if lcov is installed
...
...
HACKING
浏览文件 @
4a9ebf7d
...
@@ -2,6 +2,46 @@ Libvirt contributor guidelines
...
@@ -2,6 +2,46 @@ Libvirt contributor guidelines
==============================
==============================
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. A command similar to this
should work:
diff -urp libvirt.orig/ libvirt.modified/ > libvirt-myfeature.patch
or:
cvs diff -up > libvirt-myfeature.patch
(3) 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.
(4) Make sure your patches apply against libvirt CVS. Developers
only follow CVS and don't care much about released versions.
(5) Run the automated tests on your code before submitting any changes.
In particular, configure with compile warnings set to -Werror:
./configure --enable-compile-warnings=error
and run the tests:
make check
make syntax-check
make -C tests valgrind
The latter test checks for memory leaks.
(6) Update tests and/or documentation, particularly if you are adding
a new feature or changing the output of a program.
Code indentation
Code indentation
================
================
Libvirt's C source code generally adheres to some basic code-formatting
Libvirt's C source code generally adheres to some basic code-formatting
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录