From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Stale pages: FAQ/VariousKernelTrees OutreachyfirstpatchSetup
Date: Wed, 26 Oct 2016 08:54:51 +0200 [thread overview]
Message-ID: <20161026065451.GA21427@kroah.com> (raw)
In-Reply-To: <20161021174847.17a8c0cd@ws>
On Fri, Oct 21, 2016 at 05:48:47PM -0700, Duncan wrote:
> b) The staging tree might not be the best example for true kernel git
> sources newbies, mainline is arguably a better one.
What do you mean by "mainline"? drivers/staging/ _is_ in the mainline
kernel tree (i.e. kernel.org releases). It is a good place to find easy
coding style fixes, right?
> c) The example again appears dated and insecure, using the git://
> protocol that the git-fetch manpage's GIT URLS discussion specifically
> warns should be used with caution on unsecured networks like the
> general internet, because it does no authentication and is /not/
> secured.
Why do you need to "secure" git pulls?
thanks,
greg k-h
prev parent reply other threads:[~2016-10-26 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 0:48 Stale pages: FAQ/VariousKernelTrees OutreachyfirstpatchSetup Duncan
2016-10-26 6:54 ` Greg KH [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=20161026065451.GA21427@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.
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 NNTP newsgroup(s).