From: johnsu01 <x@x.x>
Subject: Re: Editing from Draft
Date: Thu, 12 May 2005 09:30:33 -0400 [thread overview]
Message-ID: <877ji4zi4m.fsf@ashbery.wjsullivan.net> (raw)
In-Reply-To: <v9acn0986g.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+from-uce@imap.cc> writes:
> On Wed, May 11 2005, johnsu01 wrote:
>
>> I wonder how the property got lost, though. I don't think I have ever done
>> anything to edit the properties of the draft group, and I definitely did not
>> create it by hand.
>
> If someone would be able to reproduce it, we could probably fix the bug.
I'll try to do that. I know that the question comes up occasionally on freenode
#emacs and #gnus as well.
--
-johnsu01
-http://www.wjsullivan.net
-GPG Key: AE8600B6
next prev parent reply other threads:[~2005-05-12 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 17:27 Phillip Lord
2005-05-10 6:44 ` Reiner Steib
2005-05-10 12:52 ` Phillip Lord
2005-05-10 17:16 ` Reiner Steib
2005-05-11 21:59 ` johnsu01
2005-05-12 8:09 ` Reiner Steib
2005-05-12 13:30 ` johnsu01 [this message]
2005-05-12 21:54 ` Peter TB Brett
2005-05-13 11:59 ` Phillip Lord
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=877ji4zi4m.fsf@ashbery.wjsullivan.net \
--to=x@x.x \
/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).