All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Karolina Drobnik <karolinadrobnik@gmail.com>,
	Outreachy Linux Kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Help maintain the First Patch Tutorial
Date: Tue, 19 Oct 2021 08:36:01 -0700	[thread overview]
Message-ID: <20211019153601.GA451103@alison-desk> (raw)
In-Reply-To: <YW5jiKHmi3/cjXQW@kroah.com>

On Tue, Oct 19, 2021 at 08:19:52AM +0200, Greg KH wrote:
> On Mon, Oct 18, 2021 at 10:54:20AM -0700, Alison Schofield wrote:
> > On Mon, Oct 18, 2021 at 10:59:42AM +0100, Karolina Drobnik wrote:
> > > Hi Alison,
> > > 
> > > I updated the `get_maintainer.pl` code section and split it up a bit,
> > > hope it's fine. Additionally, I decided to extract the note on
> > > `vc04_services` so it's more visible and add a comment on including the
> > > outreachy list (as a reminder).
> > > 
> > > One thing - should I use double-spaces while editing this wiki? I see
> > > they're used there, I added some in but I wouldn't be surprised if I
> > > missed some.
> > 
> > Is that the double spaces between sentences you are referring too?
> > HA HA - that shows that this writing is dated, because double space
> > between sentences, use to be the standard, but is not anymore ;)
> 
> It is still the standard for plain-text email where your email client
> shows text in fixed-width fonts.  Just like the old typewriters where
> this style was created for.
> 

Greg -

I understand the background.  I had not thought of it in terms of plain
test email, and by extension, patch logs and cover letters.  Is that a
guideline or rule for Linux Patches, or are am I just going down a rat
hole now?

Alison


  reply	other threads:[~2021-10-19 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 17:42 Help maintain the First Patch Tutorial Alison Schofield
2021-10-18  9:59 ` [Outreachy kernel] " Karolina Drobnik
2021-10-18 10:12   ` Julia Lawall
2021-10-18 14:01     ` Karolina Drobnik
2021-10-18 14:18       ` Julia Lawall
2021-10-18 17:54   ` Alison Schofield
2021-10-19  6:19     ` Greg KH
2021-10-19 15:36       ` Alison Schofield [this message]
2021-10-19 15:52         ` Greg KH
2021-10-20 13:00         ` Karolina Drobnik
2021-10-20 14:50           ` Alison Schofield
2021-10-19  9:01     ` Karolina Drobnik
2021-10-19  9:04       ` Julia Lawall
2021-10-25 11:44 ` Karolina Drobnik
2021-10-25 16:30   ` Alison Schofield
2021-10-26 12:33     ` Karolina Drobnik
2021-10-27 14:48     ` Karolina Drobnik
2021-10-27 19:20       ` Alison Schofield

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=20211019153601.GA451103@alison-desk \
    --to=alison.schofield@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=karolinadrobnik@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.