diff options
author | Fam Zheng <famz@redhat.com> | 2018-02-26 11:03:26 +0800 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2018-03-05 09:03:17 +0000 |
commit | 23500c6a9409efc80d696aede0629bfbe7556a90 (patch) | |
tree | 02e6c66eb131bab2f33c64e79b71f6f65523b320 /README | |
parent | 08bb160e02bb24e831f581f846d5f3ed2f2ce2c1 (diff) | |
download | qemu-23500c6a9409efc80d696aede0629bfbe7556a90.zip qemu-23500c6a9409efc80d696aede0629bfbe7556a90.tar.gz qemu-23500c6a9409efc80d696aede0629bfbe7556a90.tar.bz2 |
README: Document 'git-publish' workflow
Signed-off-by: Fam Zheng <famz@redhat.com>
Message-id: 20180226030326.20219-3-famz@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'README')
-rw-r--r-- | README | 31 |
1 files changed, 30 insertions, 1 deletions
@@ -56,7 +56,7 @@ The QEMU source code is maintained under the GIT version control system. git clone git://git.qemu.org/qemu.git -When submitting patches, the preferred approach is to use 'git +When submitting patches, one common approach is to use 'git format-patch' and/or 'git send-email' to format & send the mail to the qemu-devel@nongnu.org mailing list. All patches submitted must contain a 'Signed-off-by' line from the author. Patches should follow the @@ -73,6 +73,35 @@ The QEMU website is also maintained under source control. git clone git://git.qemu.org/qemu-web.git https://www.qemu.org/2017/02/04/the-new-qemu-website-is-up/ +A 'git-profile' utility was created to make above process less +cumbersome, and is highly recommended for making regular contributions, +or even just for sending consecutive patch series revisions. It also +requires a working 'git send-email' setup, and by default doesn't +automate everything, so you may want to go through the above steps +manually for once. + +For installation instructions, please go to + + https://github.com/stefanha/git-publish + +The workflow with 'git-publish' is: + + $ git checkout master -b my-feature + $ # work on new commits, add your 'Signed-off-by' lines to each + $ git publish + +Your patch series will be sent and tagged as my-feature-v1 if you need to refer +back to it in the future. + +Sending v2: + + $ git checkout my-feature # same topic branch + $ # making changes to the commits (using 'git rebase', for example) + $ git publish + +Your patch series will be sent with 'v2' tag in the subject and the git tip +will be tagged as my-feature-v2. + Bug reporting ============= |