View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001807 | unreal | ircd | public | 2004-05-11 04:43 | 2004-05-17 21:15 |
| Reporter | GouraudShading | Assigned To | |||
| Priority | normal | Severity | text | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2 | ||||
| Summary | 0001807: /close | ||||
| Description | It's a very little mistake: *** Notice -- TuX[AWAY][email protected] closed 1 unknown connections You should replace the connections word to connection(s), or parse, that one or more unknown connections closed. | ||||
| 3rd party modules | |||||
|
|
Why bother? And, as with "is a secure connection" "is on a secure connection"... it may break things. |
|
|
No, this is ok to change because it's a notice :P. |
|
|
bah meh ok. :) just trying to be helpful. |
|
|
Well I agree with w00t, it shouldn't be changed. You're right, it is a notice, but 2 messages are displayed. The /close'er gets a RPL_CLOSEEND and all ops get the NOTICE. I think it would be more confusing if one was correct and the other was not. /* 363 RPL_CLOSEEND */ ":%s 363 %s %d: Connections Closed", That would need changing too, and then we are introducing issues. |
|
|
Well I disagree, but then again I don't f*cking care! :P |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-05-11 04:43 | GouraudShading | New Issue | |
| 2004-05-12 20:16 | w00t | Note Added: 0006219 | |
| 2004-05-12 21:46 | syzop | Note Added: 0006221 | |
| 2004-05-13 01:23 | w00t | Note Added: 0006222 | |
| 2004-05-13 11:49 |
|
Note Added: 0006238 | |
| 2004-05-13 12:26 | syzop | Note Added: 0006239 | |
| 2004-05-17 21:15 | syzop | Status | new => closed |
