X2Go - everywhere@home

User Tools

Site Tools

Trace:
wiki:bugs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
wiki:bugs [2014/03/05 12:18]
ncryer [Bug submission with a Patch] 		wiki:bugs [2014/08/04 17:18]
sunweaver [Bug submitter used a non-appropriate title]
Line 28: Line 28:
 Subject: <a-really-good-short-description-of-the-problem> Subject: <a-really-good-short-description-of-the-problem>
 Body: Body:
-""" 
 Package: <name-of-x2go-component> Package: <name-of-x2go-component>
 Version: <a.b.c.d> Version: <a.b.c.d>
  
 <your-not-too-long-description-of-the-discovered-problem> <your-not-too-long-description-of-the-discovered-problem>
-""" 
 </code> </code>
  
Line 40: Line 38:
 In case you can provide a patch with your bug report, please attach the patch to your bug report. Do __not__ copy+paste the patch into the mail body, as the result will not be usable!!! In case you can provide a patch with your bug report, please attach the patch to your bug report. Do __not__ copy+paste the patch into the mail body, as the result will not be usable!!!
  
-Create patches for master branch and send them in git format. The documentation about creating git patches can be found [[http://www.git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project|here]] +Create patches for master branch and send them in git format. The documentation about creating git patches can be found [[http://www.git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Public-Large-Project|here]] 
  
 Some of you have their own Git clones of X2Go Git. If you want to provide a patch via your public Git clone of an X2Go component, please make sure that the patch is just one commit on one of your Git branches. The rule here is simple: one Git commit on your side, one bug report in X2Go BTS. Everything else will take too much time on the patch reviewer side. Some of you have their own Git clones of X2Go Git. If you want to provide a patch via your public Git clone of an X2Go component, please make sure that the patch is just one commit on one of your Git branches. The rule here is simple: one Git commit on your side, one bug report in X2Go BTS. Everything else will take too much time on the patch reviewer side.
Line 50: Line 48:
 Subject: <a-really-good-short-description-of-the-problem> Subject: <a-really-good-short-description-of-the-problem>
 Body: Body:
-""" 
 Package: <name-of-x2go-component> Package: <name-of-x2go-component>
 Version: <a.b.c.d> Version: <a.b.c.d>
Line 56: Line 53:
  
 <your-not-too-long-description-of-the-discovered-problem> <your-not-too-long-description-of-the-discovered-problem>
-"""+
 Attachment: <your-patch.diff> Attachment: <your-patch.diff>
 </code> </code>
Line 68: Line 65:
 Subject: <a-really-good-short-description-of-the-problem> Subject: <a-really-good-short-description-of-the-problem>
 Body: Body:
-""" 
 Package: <name-of-x2go-component> Package: <name-of-x2go-component>
 Version: <a.b.c.d> Version: <a.b.c.d>
Line 74: Line 70:
  
 <your-not-too-long-description-of-the-discovered-problem> <your-not-too-long-description-of-the-discovered-problem>
-""" 
 </code> </code>
  
Line 99: Line 94:
 <code> <code>
 To: <nnn>@bugs.x2go.org To: <nnn>@bugs.x2go.org
-Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org+Cc: <nnn>-submitter@bugs.x2go.org
 Subject: Issue resolved in <x2go-component> <version> Subject: Issue resolved in <x2go-component> <version>
 Body: Body:
-""" +Control: close -1
-close #<nnn> +
-thanks+
  
 The reported issue has been resolved in the lately release version <version> of <x2go-component>. The reported issue has been resolved in the lately release version <version> of <x2go-component>.
Line 110: Line 103:
 Thanks for reporting this issue, Thanks for reporting this issue,
 <my-name> <my-name>
-""" 
 </code> </code>
  
Line 119: Line 111:
 <code> <code>
 To: <nnn>@bugs.x2go.org To: <nnn>@bugs.x2go.org
-Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org+Cc: <nnn>-submitter@bugs.x2go.org
 Subject: <a-good-subject-line> Subject: <a-good-subject-line>
 Body: Body:
-""" +Control: reassign -1 <another-x2go-component>
-reassign #<nnn> <another-x2go-component> +
-thanks+
  
 The reported issue is actually a bug in <another-x2go-component>. Reassigning. The reported issue is actually a bug in <another-x2go-component>. Reassigning.
Line 132: Line 122:
 Thanks for reporting this issue, Thanks for reporting this issue,
 <my-name> <my-name>
-""" 
 </code> </code>
  
Line 142: Line 131:
 <code> <code>
 To: <nnn>@bugs.x2go.org To: <nnn>@bugs.x2go.org
-Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org+Cc: <nnn>-submitter@bugs.x2go.org
 Subject: <a-good-subject-line> Subject: <a-good-subject-line>
 Body: Body:
-""" +Control: retitle -1 <better-title>
-retitle #<nnn> <better-title> +
-thanks+
  
 <further-info-if-any> <further-info-if-any>
Line 153: Line 140:
 Thanks for reporting this issue, Thanks for reporting this issue,
 <my-name> <my-name>
-""" 
 </code> </code>
  
Line 166: Line 152:
 Subject: <cloning-this-bug-for-a-reason> Subject: <cloning-this-bug-for-a-reason>
 Body: Body:
-""" 
 clone #<nnn> -1 clone #<nnn> -1
 tag -1 - pending tag -1 - pending
Line 178: Line 163:
 Best, Best,
 <my-name> <my-name>
-""" 
 </code> </code>
  
  
  
wiki/bugs.txt · Last modified: 2018/05/24 17:19 by stefanbaur

Page Tools

Imprint & Legal Disclaimer - Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki