All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: outreachy@lists.linux.dev
Subject: Should we Cc this list when submitting patches for subsystems other than "staging"?
Date: Tue, 12 Apr 2022 22:21:31 +0200	[thread overview]
Message-ID: <1859502.6tgchFWduM@leap> (raw)

Hello,

During the current month I have submitted some patches for subsystems other
than drivers/staging. When I sent them I thought that those shouldn't be 
Cc'ed also to this list. Now I'm not anymore sure if I did it correctly.

My question is if all patches sent by the Outreachy's applicants until 
April 22nd should also be sent to this list, even when they are for 
subsystems other than drivers/staging.

Furthermore, one of the above-mentioned patches is strictly related to one
of the three Linux projects, being it a reworking and extension of a large 
section of the documentation of HIGHMEM. Is it sufficient to add that patch 
to the page where we register our contributions in the Outreachy's website? 

I'm also asking because during these days I'm preparing further patches to
other subsystems and I'm going to submit them well before April 22nd. 

Thanks,

Fabio M. De Francesco



             reply	other threads:[~2022-04-12 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 20:21 Fabio M. De Francesco [this message]
2022-04-12 22:36 ` Should we Cc this list when submitting patches for subsystems other than "staging"? Alison Schofield
     [not found]   ` <CAMWRUK6W4-3Fwh7BAQ_aSWYG4Dh=oSX-ZKgHuiO0QhKUwyCEOA@mail.gmail.com>
2022-04-13  4:15     ` Alison Schofield
2022-04-13 15:14       ` Sevinj Aghayeva
2022-04-13 15:28         ` Alison Schofield
2022-04-13 16:19           ` Roopa Prabhu
2022-04-13  7:09   ` Fabio M. De Francesco
2022-04-13 14:58     ` 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=1859502.6tgchFWduM@leap \
    --to=fmdefrancesco@gmail.com \
    --cc=outreachy@lists.linux.dev \
    /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.