outreachy.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: outreachy@lists.linux.dev
Subject: [outreachy] more about applications
Date: Sun, 29 Oct 2023 13:22:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2310291318181.3136@hadrien> (raw)

I think it was not made clear anywhere, but a contribution is a patch that
has been accepted into the Linux kernel.  So that it is obvious that this
is the case, you can best include links to your patches in Greg's tree,
not links to lore where you submitted the patch.

To get a link to Greg's tree, you can go to the following URL:

https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/tree/?h=staging-testing

In the upper right hand corner, there is a pull down menu that says log
message and a button that says Search.  Change log message to author and
type your name in the box.  Then you will get a link to each of your
patches.

If you don't see this message in time to update your application, we will
look up the information for you.

thanks,
julia

                 reply	other threads:[~2023-10-29 12:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.DEB.2.22.394.2310291318181.3136@hadrien \
    --to=julia.lawall@inria.fr \
    --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 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).