From: rhkramer@gmail.com
To: vsnsdualce2@redchan.it
Cc: debian-user@lists.debian.org, linux-kernel@vger.kernel.org,
Ivan Ivanov <qmastery16@gmail.com>,
mailinglists@mattcrews.com, jhasler@newsguy.com,
scdbackup@gmx.net, richard@walnut.gen.nz, curty@free.fr,
jmtd@debian.org, mick.crane@gmail.com, tomas@tuxteam.de,
steve@einval.com, joe@jretrading.com, rms@gnu.org,
esr@thyrsus.com
Subject: Re: Can a recipients rights under GNU GPL be revoked? - Bradley M. Kuhn is not an attorney (he should go get his JD and get licensed).
Date: Sun, 5 May 2019 08:07:51 -0400 [thread overview]
Message-ID: <201905050807.51462.rhkramer@gmail.com> (raw)
In-Reply-To: <60c1b08305c5326e3503f51d81622541@redchan.it>
On Sunday, May 05, 2019 12:51:15 AM vsnsdualce2@redchan.it wrote:
> Bar rules do not allow lawyers to serve under a non-lawyer
> in
> an organization, and the organization was essentially a pro-bono law
> firm
> (which really needed a attorney in it's ranks...)
That's interesting, but (off the point of this email exchange), it puzzles me
-- many corporations headed by non-lawyers have lawyers on staff, so I'm
guessing that the statement you made applies only to organizations like law
firms, or, the lawyers on the staff of a non-law corporation are in something at
least a little different than the normal employer / employee relationship.
(PS: I stand corrected on Kuhn being a lawyer -- thanks for the correction.)
Now I have to debate (with myself) whether to prune the cc list -- I forget
the original post -- was it really this widespread?
next prev parent reply other threads:[~2019-05-05 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 4:51 Can a recipients rights under GNU GPL be revoked? - Bradley M. Kuhn is not an attorney (he should go get his JD and get licensed) vsnsdualce2
2019-05-05 12:07 ` rhkramer [this message]
2019-05-05 12:25 ` Steve McIntyre
2019-05-05 17:43 ` vsnsdualce2
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=201905050807.51462.rhkramer@gmail.com \
--to=rhkramer@gmail.com \
--cc=curty@free.fr \
--cc=debian-user@lists.debian.org \
--cc=esr@thyrsus.com \
--cc=jhasler@newsguy.com \
--cc=jmtd@debian.org \
--cc=joe@jretrading.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglists@mattcrews.com \
--cc=mick.crane@gmail.com \
--cc=qmastery16@gmail.com \
--cc=richard@walnut.gen.nz \
--cc=rms@gnu.org \
--cc=scdbackup@gmx.net \
--cc=steve@einval.com \
--cc=tomas@tuxteam.de \
--cc=vsnsdualce2@redchan.it \
/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