unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Bengt Richter <bokr@bokr.com>
Cc: guix-devel@gnu.org
Subject: Re: [BLOG] rust blog post
Date: Wed, 27 Nov 2019 11:38:49 +0200	[thread overview]
Message-ID: <20191127093849.GN1124@E5400> (raw)
In-Reply-To: <20191127001901.GB1044@PhantoNv4ArchGx.localdomain>

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

On Tue, Nov 26, 2019 at 04:19:01PM -0800, Bengt Richter wrote:
> Hi Pierre, and apologies to Efraim...
> 
> On +2019-11-26 14:01:10 +0100, Pierre Neidhardt wrote:
> > Bengt Richter <bokr@bokr.com> writes:
> > 
> > >     be a binary. Its... both? Javascript libraries leave  distro
> > 
> > Typo: "It's".
> >

It's one of the ones I have a hard time with. When I remember I'm great
with it.

> 
> I noticed that too, but it's Efraim's typo,
> as is the entire text: I merely reformatted Efraim's post
> into a sort of rfc-style, i.e., Left-and-Right-justified.

Thanks

> 
> So, credit to Efraim for the:
> 
> > Interesting read, thanks for sharing.
> > Do you intend to publish it on Guix' blog?  If so, I think the tone
> > might come across as a little bit too "rantish", maybe make it a little
> > more neutral / balanced.

Definitely wasn't aiming for rantish, I'll see what I can do about
making it better. It was more of a stream-of-consciousness typing and I
figured I could go back and rework it later.

> > 
> > I'd also elaborate the intro / conclusion to make the context a bit
> > clearer and maybe explain what you think should be done.

Sounds like a good idea.

> > 
> > Cheers!
> > 
> > -- 
> > Pierre Neidhardt
> > https://ambrevar.xyz/
> 
> Efraim, thanks for your work -- I didn't mean to hijack it, honest :)
> Sorry for not making it clear that I was just reformatting your post ;-/
> 
> Ah, perhaps Pierre merely clicked reply-all and he really was thanking you, Efraim,
> and it just appeared to be directed toward me because of the "> Bengt Richter <bokr@bokr.com> writes:"
> heading?

Likely. I normally hit reply-all for mailing list posts

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-11-27  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 10:30 [BLOG] rust blog post Efraim Flashner
2019-11-26  9:58 ` Pierre Neidhardt
2019-11-26 10:27   ` Efraim Flashner
2019-11-26 12:26     ` Bengt Richter
2019-11-26 13:01       ` Pierre Neidhardt
2019-11-27  0:19         ` Bengt Richter
2019-11-27  9:38           ` Efraim Flashner [this message]

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=20191127093849.GN1124@E5400 \
    --to=efraim@flashner.co.il \
    --cc=bokr@bokr.com \
    --cc=guix-devel@gnu.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.
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).