diff options
| author | K. Handa | 2016-01-08 23:21:43 +0900 |
|---|---|---|
| committer | K. Handa | 2016-01-08 23:21:43 +0900 |
| commit | f36805424633e3acb48ed9f0f729a36760e4cb7f (patch) | |
| tree | 555f0e21f19aeee47d2855a5c7700afec5c81386 /admin | |
| parent | bc9a28ab424647209cc2f91ad21cdb41a7052812 (diff) | |
| parent | 4580671f5e2a68885e0fca93eeaf9daaeebe82b3 (diff) | |
| download | emacs-f36805424633e3acb48ed9f0f729a36760e4cb7f.tar.gz emacs-f36805424633e3acb48ed9f0f729a36760e4cb7f.zip | |
Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/notes/triage | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/admin/notes/triage b/admin/notes/triage index bc91b6c26f7..5b0e35c144c 100644 --- a/admin/notes/triage +++ b/admin/notes/triage | |||
| @@ -57,7 +57,7 @@ For each new bug, ask the following questions: | |||
| 57 | 1. Is the bug report written in a way to be easy to reproduce (starts from | 57 | 1. Is the bug report written in a way to be easy to reproduce (starts from |
| 58 | emacs -Q, etc.)? If not, ask the reporter to try and reproduce it on an | 58 | emacs -Q, etc.)? If not, ask the reporter to try and reproduce it on an |
| 59 | emacs without customization. | 59 | emacs without customization. |
| 60 | 2. Is the bug report written against the lastest emacs? If not, try to | 60 | 2. Is the bug report written against the latest emacs? If not, try to |
| 61 | reproduce on the latest version, and if it can't be reproduced, ask the | 61 | reproduce on the latest version, and if it can't be reproduced, ask the |
| 62 | reporter to try again with the latest version. | 62 | reporter to try again with the latest version. |
| 63 | 3. Is the bug the same as another bug? If so, merge the bugs. | 63 | 3. Is the bug the same as another bug? If so, merge the bugs. |