From: Ted Zlatanov <tzz@lifelogs.com>
To: jidanni@jidanni.org
Cc: ding@gnus.org
Subject: Re: keep Gcc: field in buffer after sending
Date: Wed, 12 Dec 2007 06:45:26 -0600 [thread overview]
Message-ID: <86r6hsf5eh.fsf@lifelogs.com> (raw)
In-Reply-To: <874peo48s2.fsf@jidanni.org> (jidanni@jidanni.org's message of "Wed, 12 Dec 2007 16:27:57 +0800")
On Wed, 12 Dec 2007 16:27:57 +0800 jidanni@jidanni.org wrote:
TZ> That's good, but did you test the patch itself? I won't commit it until
TZ> at least one user has tested it...
j> $ patch gnus-msg.el patch
j> patching file gnus-msg.el
j> Hunk #2 FAILED at 1635.
j> 1 out of 2 hunks FAILED -- saving rejects to file gnus-msg.el.rej
j> $ apt-cache policy emacs22-el
j> Installed: 22.1+1-2.2
j> 500 http://linux.cdpa.nsysu.edu.tw sid/main Packages
j> That's right, I have not implemented a cutting edge version test bed,
j> so, "I trust that your patch must work".
It's not a problem with me that you are not willing to test the latest
Gnus, but you must realize that the patch will not go into the CVS tree
until at least one user has tested it. I tried testing it but the reply
buffer was killed after I hit `C-c C-c'; I don't know how to prevent
that and I didn't have the time to look into it further.
Also, Reiner's note about the ignored headers variables might make a
difference for the patch.
Ted
next prev parent reply other threads:[~2007-12-12 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 5:03 jidanni
2007-12-11 16:31 ` Ted Zlatanov
2007-12-11 19:02 ` jidanni
2007-12-11 23:01 ` Ted Zlatanov
2007-12-12 8:27 ` jidanni
2007-12-12 12:45 ` Ted Zlatanov [this message]
2007-12-12 13:16 ` Miles Bader
2007-12-12 13:26 ` Ted Zlatanov
2007-12-12 19:44 ` Reiner Steib
2007-12-12 20:46 ` Ted Zlatanov
2007-12-11 22:08 ` Reiner Steib
2007-12-11 23:10 ` Ted Zlatanov
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=86r6hsf5eh.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.org \
/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).