From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Fwd: E-mail attachments and local names
Date: 26 Jul 1999 18:58:14 +0200 [thread overview]
Message-ID: <87so6bgxg9.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Robert Bihlmeyer's message of "24 Jul 1999 16:22:27 +0200"
Robert Bihlmeyer <robbe@orcus.priv.at> writes:
> It seems that the user should be able to rename the attachment for
> the purposes of the message or that the file should just be called
> attachment1, attachment2, ...
I agree that there should be an option to do that. I usually store my
patches in a dummy file like `fl', which is short and makes sense for
me, but looks quite ugly in the resulting MIME message.
next prev parent reply other threads:[~1999-07-26 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-24 14:22 Robert Bihlmeyer
1999-07-26 16:58 ` Hrvoje Niksic [this message]
1999-07-27 12:29 ` Kai Großjohann
1999-07-27 14:48 ` David S. Goldberg
1999-08-27 21:57 ` Lars Magne Ingebrigtsen
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=87so6bgxg9.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).