From: Eze Ogwuma <typhoon@dircon.co.uk>
Subject: Re: Gnus v5.6.40 is released
Date: 27 Aug 1998 19:15:44 +0100 [thread overview]
Message-ID: <m3af4qi94f.fsf@localhost.localdomain> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1998 09:31:01 +0200"
Hi,
This patch doesn't appear to apply properly.
Here's the output.
patching file `texi/ChangeLog'
patching file `lisp/ChangeLog'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to lisp/ChangeLog.rej
patching file `lisp/gnus-agent.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to lisp/gnus-agent.el.rej
patching file `lisp/gnus-art.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to lisp/gnus-art.el.rej
patching file `lisp/gnus-cache.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to lisp/gnus-cache.el.rej
patching file `lisp/gnus-group.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to lisp/gnus-group.el.rej
patching file `lisp/gnus-spec.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to lisp/gnus-spec.el.rej
patching file `lisp/gnus-srvr.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to lisp/gnus-srvr.el.rej
patching file `lisp/gnus-sum.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to lisp/gnus-sum.el.rej
patching file `lisp/gnus-uu.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to lisp/gnus-uu.el.rej
patching file `lisp/gnus.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to lisp/gnus.el.rej
patching file `lisp/message.el'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to lisp/message.el.rej
patching file `texi/gnus.texi'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
9 out of 9 hunks ignored -- saving rejects to texi/gnus.texi.rej
patching file `texi/message.texi'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to texi/message.texi.rej
patching file `texi/ChangeLog'
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to texi/ChangeLog.rej
--
Eze Ogwuma
prev parent reply other threads:[~1998-08-27 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-27 7:31 Lars Magne Ingebrigtsen
1998-08-27 18:15 ` Eze Ogwuma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3af4qi94f.fsf@localhost.localdomain \
--to=typhoon@dircon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).