diff options
| author | Matthew Sackman <matthew@rabbitmq.com> | 2011-03-29 11:27:29 +0100 |
|---|---|---|
| committer | Matthew Sackman <matthew@rabbitmq.com> | 2011-03-29 11:27:29 +0100 |
| commit | e3992edc4eaac0955fcb63012e7eed59596def1e (patch) | |
| tree | e60158c8ebb7ab5b7cc3723d61a2fa2d4b7d597e | |
| parent | 3a7a409084c522cd94d74fc251a3a5b11fbe690e (diff) | |
| download | rabbitmq-server-git-e3992edc4eaac0955fcb63012e7eed59596def1e.tar.gz | |
english
| -rw-r--r-- | src/rabbit_backing_queue.erl | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/rabbit_backing_queue.erl b/src/rabbit_backing_queue.erl index fe09e40042..0ca8d260ef 100644 --- a/src/rabbit_backing_queue.erl +++ b/src/rabbit_backing_queue.erl @@ -90,11 +90,11 @@ behaviour_info(callbacks) -> %% %% It is legal for the same message id to appear in the results %% of multiple calls to drain_confirmed, which means that the - %% backing queue is not required to keep track of the which - %% messages it has already confirmed. The confirm will be issued - %% to the publisher the first time the message id appears in the - %% result of drain_confirmed. All subsequent appearances of that - %% message id will be ignored. + %% backing queue is not required to keep track of which messages + %% it has already confirmed. The confirm will be issued to the + %% publisher the first time the message id appears in the result + %% of drain_confirmed. All subsequent appearances of that message + %% id will be ignored. {drain_confirmed, 1}, %% Drop messages from the head of the queue while the supplied |