Module: docs
Branch: master
Commit: 202921eaeb4935069b98352ac786930154006d38
URL: http://source.winehq.org/git/docs.git/?a=commit;h=202921eaeb4935069b98352ac…
Author: André Hentschel <nerv(a)dawncrow.de>
Date: Mon Jul 4 22:08:14 2011 +0200
winedev: Update git usage for patch creation.
---
en/winedev-coding.sgml | 13 +++++--------
1 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml
index 430e602..2dc12a6 100644
--- a/en/winedev-coding.sgml
+++ b/en/winedev-coding.sgml
@@ -46,19 +46,16 @@
To generate a patch using Git, first commit it to your local tree.
</para>
<para>
- Each file that you change needs to be updated with
- <command> git update </command>. If you are adding or removing
- a file, use <command> git update --add </command> or
- <command>git update --remove</command> respectively.
- After updating the index, commit the change using
- <command> git commit </command>. The commit message will be
- sent with your patch, and recored in the ChangeLog.
+ If you are adding a file, use <command>git add</command>.
+ Commit the change using <command>git commit</command>. The
+ commit message will be sent with your patch, and recorded in
+ the commit log.
</para>
<para>
After committing the patch, you can extract it using
<command>git format-patch</command> and send it to wine-patches
using <command>git imap-send</command> or simply attaching it
- to you mail manually.
+ to your mail manually.
</para>
</sect1>
Module: docs
Branch: master
Commit: 785929d918ce23baee3baaf1ce06400d13753b3e
URL: http://source.winehq.org/git/docs.git/?a=commit;h=785929d918ce23baee3baaf1c…
Author: André Hentschel <nerv(a)dawncrow.de>
Date: Mon Jul 4 22:09:11 2011 +0200
winedev: A hint for patch separation.
As suggested by Jerome Leclanche.
---
en/winedev-coding.sgml | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml
index 469642f..430e602 100644
--- a/en/winedev-coding.sgml
+++ b/en/winedev-coding.sgml
@@ -211,6 +211,10 @@ code
is your friend!
</para>
<para>
+ Patches must not break building Wine or cause test failures.
+ Adding dead code should also be avoided.
+ </para>
+ <para>
Save yourself some embarrassment and run your patched code
against more than just your current test example. Experience
will tell you how much effort to apply here. If there are