public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: media-gfx/blender-2.71 dependencies
Date: Wed, 9 Jul 2014 16:44:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140709T183456-241@post.gmane.org> (raw)
In-Reply-To: 755C16BF-3AC1-4A73-A771-9BAE929C87DC@stellar.eclipse.co.uk

Stroller <stroller <at> stellar.eclipse.co.uk> writes:


> Please don't use pastebin sites - if your output is too long to copy and
paste into the body of the message,
> then please attach it as a plain text file. If you name it output.txt then
most people, with GUI mail
> clients, will be able to read it just by double-clicking.

> Most pastebin services expire old pastes periodically (not to mention that
pastebin services are hardly
> profitable, and close down all the time) whereas these mailing list
messages are archived in multiple
> places and are referenced for years. 

> If you attach these files as plain text then they'll be archived, useful
to other people with the same
> problem in the future.

I'll agree, this is excellent advise. However, I use game.org to read
and post to gentoo-user. So how do you attached a txt file to
those postings via gmane? Options to get the txt file attachemnent into the 
proper record?

Gmane refuses to post long replies. Gmane allows one to read and post
from a variety of machines, particularly useful when one locks up 
one's main workstation, which I have done of several occasions, and have
to use gmane to recover with the aid of the gentoo-user list:

http://news.gmane.org/gmane.linux.gentoo.user


curiously,
James



  parent reply	other threads:[~2014-07-09 16:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  5:14 [gentoo-user] media-gfx/blender-2.71 dependencies List Reader
2014-07-09  5:18 ` Dan O.
2014-07-09  6:05   ` List Reader
2014-07-09  7:54   ` List Reader
2014-07-09 13:14     ` Alan McKinnon
2014-07-10  3:11       ` List Reader
2014-07-10 11:51         ` Stroller
2014-07-10 15:31           ` Alan McKinnon
2014-07-10 18:11             ` List Reader
2014-07-10 18:53               ` Alan McKinnon
2014-07-10 19:42                 ` Dale
2014-07-10 20:26                   ` Alan McKinnon
2014-07-13 16:10                     ` Dale
2014-07-11  3:06                 ` List Reader
2014-07-10 21:01           ` [gentoo-user] " James
2014-07-11  2:56             ` List Reader
2014-07-10 19:55   ` [gentoo-user] " J. Roeleveld
2014-07-11  0:37     ` Dan Oriani
2014-07-09 11:02 ` Stroller
2014-07-09 14:33   ` List Reader
2014-07-09 15:21   ` List Reader
2014-07-10 11:30     ` Stroller
2014-07-09 16:44   ` James [this message]
2014-07-09 20:06     ` [gentoo-user] " Alan McKinnon
2014-07-09 20:48       ` James
2014-07-10  9:48         ` Alan McKinnon
2014-07-10 10:11           ` Neil Bothwick
2014-07-10 11:41             ` Alan McKinnon
2014-07-10 13:26               ` Neil Bothwick
2014-07-10 15:00                 ` Alan McKinnon
2014-07-10 14:52               ` James
2014-07-10 15:04                 ` Alan McKinnon
2014-07-10 20:02               ` J. Roeleveld
2014-07-10 11:32     ` [gentoo-user] " Stroller

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=loom.20140709T183456-241@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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