unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: tree doesn't get called
Date: Mon, 8 May 2017 19:28:57 +0200	[thread overview]
Message-ID: <CAJ98PDwb_4fNAO4osXn51FZ22gh1gOh69dEffoOnYy23-GW=Eg@mail.gmail.com> (raw)
In-Reply-To: <87fugfn6og.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

Mark,

2017-05-08 9:34 GMT+02:00 Mark H Weaver <mhw@netris.org>:

> Catonano <catonano@gmail.com> writes:
> > So here's the package
> > http://paste.lisp.org/display/345871
> >
> > What is wrong with it ?
>
> Please always include the relevant code snippets in the email itself,
> rather than using a paste site.  Paste sites are useful for contexts
> such as IRC where pasting more than a few lines is inconvenient and
> generally frowned upon, and where the discussions are ephemeral.
>
> On the other hand, these email lists are archived and we would like the
> archives to be comprehensible to future readers.  That will not be
> possible for the emails in this thread after the code under discussion
> has been deleted from the paste site, or the paste site goes offline.
>
> There are also privacy implications to forcing the readers of your email
> to click on a link, thus creating network traffic and a log on someone's
> server, in order to see the core content of your message.
>
> What do you think?
>

I'm ready to adhere to any guidelines set set by the community

I have no problem in pasting pieces of code directly in the emails body

I just hadn't considered the concerns you are raising

In fact, I'd paste code even on IRC channels, I don't do so because I have
been requested to abstain from pasting code in chat channels in the past

But I don't understand the reason why that is not desirable, inconvenient
and frown upon.

I just adhere to a costme that seems to be common and widely accepted, or
even assumed.

I can do te same for mailing lists of course. I just thought the set of
assumptions was the same

So I will follow your lead in the future, I have begun already !

In this same thread I reported errors and pieces of code pasting the wole
thing in the email body

It's even more practical, like this !

[-- Attachment #2: Type: text/html, Size: 2684 bytes --]

  reply	other threads:[~2017-05-08 17:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 15:50 tree doesn't get called Catonano
2017-05-05 22:24 ` Eric Bavier
2017-05-08  5:02   ` Catonano
2017-05-08  6:08     ` Ricardo Wurmus
2017-05-08 17:14       ` Catonano
2017-05-08 17:45         ` Catonano
2017-05-08 20:19         ` Ricardo Wurmus
2017-05-09 15:41           ` Catonano
2017-05-09 15:43             ` Catonano
2017-05-10 19:51               ` Ricardo Wurmus
2017-05-11  4:20                 ` Catonano
2017-05-09 17:20             ` Ricardo Wurmus
2017-05-09 18:12               ` Catonano
2017-05-08  7:34 ` Mark H Weaver
2017-05-08 17:28   ` Catonano [this message]
2017-05-08 17:58     ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ98PDwb_4fNAO4osXn51FZ22gh1gOh69dEffoOnYy23-GW=Eg@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).