All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khadija Kamran <kamrankhadijadj@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Outreachy@lists.linux.dev
Subject: Re: Record Contributions for Outreachy
Date: Tue, 14 Mar 2023 12:18:05 +0500	[thread overview]
Message-ID: <ZBAfrfRH3OxLebjj@khadija-virtual-machine> (raw)
In-Reply-To: <ZA/LkFq1w6jf6YAR@aschofie-mobl2>

On Mon, Mar 13, 2023 at 06:19:12PM -0700, Alison Schofield wrote:

Hey Alisone!
Thank you for the help.

> Hi Khadija,
> 
> When a patch has been accepted into staging/testing it will be visible
> here: 
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/log/?h=staging-testing
> 
> Once you see a patch in staging/testing, then add it to your dashboard,
> with a link to the patch. Mentors will be able to click through and
> see the patch, but may not have followed its entire journey to getting
> merged. So, take a moment, and share a note in your dashboard explaining
> what you learned from that patch. 
> 
> We expect learnings at this point to be about patch mechanics like
> 'I learned what imperative mode is', 'I learned how to revise and
> resend a patchset', 'I learned how to keep my staging/testing branch up
> to date so I don't send patches for things already fixed'. 
>
> First Patch Tutorial updates are also contributions. Please record
> those on the dashboard also. For those, you can send a link to the
> email on this list where you proposed your update.
>

I will keep above points in mind while recording the contribution.
Thank you!

Regards,
Khadija

> Thanks,
> Alison

      reply	other threads:[~2023-03-14  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 20:36 Record Contributions for Outreachy Khadija Kamran
2023-03-14  1:19 ` Alison Schofield
2023-03-14  7:18   ` Khadija Kamran [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZBAfrfRH3OxLebjj@khadija-virtual-machine \
    --to=kamrankhadijadj@gmail.com \
    --cc=Outreachy@lists.linux.dev \
    --cc=alison.schofield@intel.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.