From: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
To: git <git@vger.kernel.org>
Subject: http://yro.slashdot.org/article.pl?sid=10/09/21/2315251
Date: Wed, 22 Sep 2010 11:20:48 +0100 [thread overview]
Message-ID: <AANLkTikfC4SLPaEHt8FGm=tYBfrYM2qjttGy+z-i_Kus@mail.gmail.com> (raw)
i trust that nobody will make the comment "but source code couldn't
possibly be considered dangerous enough to block using ACTA" and this
might go some way towards explaining one - not all - one i repeat just
one of the factors why i believe that free software development
_needs_ tools which can side-step single-point-of-failure locations
that can be blocked by stupid fucking "agreements" like ACTA.
l.
reply other threads:[~2010-09-22 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='AANLkTikfC4SLPaEHt8FGm=tYBfrYM2qjttGy+z-i_Kus@mail.gmail.com' \
--to=luke.leighton@gmail.com \
--cc=git@vger.kernel.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).