diff options
| author | Andrew Chilton <andychilton@gmail.com> | 2008-07-04 16:17:34 +1200 |
|---|---|---|
| committer | Andrew Chilton <andychilton@gmail.com> | 2008-07-04 16:21:29 +1200 |
| commit | 2979e8914aa542a20cbf07e8f7812e293ad0699d (patch) | |
| tree | d2032a7117a0efc566ff0e50408b2068cd006af2 /README | |
| parent | 41ec963c1aace994072b6d62b20cdce5370e0e8e (diff) | |
| parent | f6649a52ff5610af925818cddd720fa5945bd6b3 (diff) | |
Merge branch 'upstream'
Diffstat (limited to 'README')
| -rw-r--r-- | README | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -38,6 +38,7 @@ When listing the issues, they can also be filtered: $ cil list --label=Type-Enhancement $ cil list --is-open $ cil list --label=Milestone-v0.3 --is-open + $ cil list --is-mine You can see what the issue name is by looking at the 'Issue' title. Imagine it is 'cafebabe' (which by default is the time from epoch). To see your issue @@ -81,6 +82,15 @@ it from the issue: $ cil extract decaf7ea --filename=mycore +If someone sends you a bug report or a comment via email and you wish to import +it into your issues list, you can use the 'am' command to do it's best to +import it. It will try and figure out if an issue is already mentioned and if +so, will try and import the email as a comment for that particular issue. In +the case where an existing issue is not found, it will import the email as a +new issue: + + $ cil am email.txt + Finally, because the cil issue files reside on the filesystem in flat files, there needs to be a way to check the integrity of the issues, therefore you can run this to do checks regarding the whole issue list: |