unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: “Guix Profiles in Practice”
Date: Sat, 26 Oct 2019 20:29:37 -0700	[thread overview]
Message-ID: <20191027032937.GA990@PhantoNv4ArchGx.localdomain> (raw)
In-Reply-To: <87o8y3ltc1.fsf@ambrevar.xyz>

Hi Pierre,

On +2019-10-26 12:00:30 +0200, Pierre Neidhardt wrote:
> "Thompson, David" <dthompson2@worcester.edu> writes:
> 
> > Great article!
> 
> Thanks! :)
> 
> > I spotted a typo in the first paragraph: "on a same system" should be
> > "on the same system."
> 
> I can fix it.  Out of curiosity, why is it wrong?  "All users on a
> system..."  is correct, "All users on a given system" too, so I wonder
> why "on a same system" would not be.  What I meant here is "the same
> unspecified system".
> 
[...]

How would you say it in French? (I'm trying to recall high school French here, so be kind ;-)

I think english "a" is like French "un" or "une" -- so translating "on a same system" literally
(using my flawed French), does "en un même système" sound right to you?

It doesn't to me, unless même has a sense of pareil used that way.
Maybe "en utilisant le même système" ? (note le/the -- not un/a)
--
Regards,
Bengt Richter

  reply	other threads:[~2019-10-27  3:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 10:24 “Guix Profiles in Practice” Ludovic Courtès
2019-10-25 16:36 ` Thompson, David
2019-10-25 20:44   ` Pjotr Prins
2019-10-26 10:02     ` Pierre Neidhardt
2019-10-27  8:56       ` Pjotr Prins
2019-10-27 11:30         ` Pierre Neidhardt
2019-10-27 11:43           ` Hartmut Goebel
2019-10-27 20:06           ` Konrad Hinsen
2019-10-27 21:05             ` Pierre Neidhardt
2019-10-28 16:20               ` Konrad Hinsen
2019-10-30  8:36     ` Pierre Neidhardt
2019-10-26  0:34   ` Jonathan Frederickson
2019-10-26  1:19     ` Jonathan Frederickson
2019-10-26 10:00   ` Pierre Neidhardt
2019-10-27  3:29     ` Bengt Richter [this message]
2019-10-27  8:49       ` Pierre Neidhardt
2019-10-27 13:33     ` Konrad Hinsen
2019-10-27 13:53       ` Jelle Licht
2019-11-03 14:24   ` Ludovic Courtès
2019-11-03 16:49     ` Jonathan Frederickson
2019-11-04 10:12       ` Pierre Neidhardt
2019-11-04 14:33       ` Ludovic Courtès
2019-11-04 10:10     ` Pierre Neidhardt
2019-11-05 22:18       ` Carlo Zancanaro
2019-11-06  8:32         ` Pierre Neidhardt
2019-11-06 17:37           ` Ludovic Courtès
2019-11-07 12:42             ` Pierre Neidhardt
2019-10-26 18:32 ` Alex Griffin
2019-10-26 19:38   ` Pierre Neidhardt
  -- strict thread matches above, loose matches on Subject: below --
2019-11-02 18:51 Tanguy Le Carrour
2019-11-02 19:21 ` Pierre Neidhardt

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=20191027032937.GA990@PhantoNv4ArchGx.localdomain \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).