public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Berntsen <alexander@plaimi.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: devmanual moved to github
Date: Mon, 13 May 2013 14:42:58 +0200	[thread overview]
Message-ID: <5190DFD2.5000201@plaimi.net> (raw)
In-Reply-To: <20130513123822.GB30978@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 13/05/13 14:38, Greg KH wrote:
> Linux does not use GitHub for anything, but a lot of users do use
> the copy of the kernel tree on GitHub for their own development,
> which has nothing to do with the main Linux kernel developer
> workflow.
I misremembered a discussion Linus had in which he said GitHub was
great for hosting (but terrible for stuff like commit messages).
Thanks for correcting me.

My point about using GitHub for hosting only still stands.
- -- 
Alexander
alexander@plaimi.net
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlGQ39IACgkQRtClrXBQc7VizwEAkgYzCZOTO6dPO7Y2j594Z/8j
az6l1qrjWA2j9LiUf7IA/RfA+QGbp9Y+p97DoxX+Qr3BrhE/0XkrZo10YQJDlN++
=b0s3
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-05-13 12:43 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 11:32 [gentoo-dev] devmanual moved to github Markos Chandras
2013-05-12 13:12 ` Rich Freeman
2013-05-12 13:27   ` Peter Stuge
2013-05-12 15:02     ` Ben de Groot
2013-05-12 15:15       ` Markos Chandras
2013-05-12 15:12     ` Diego Elio Pettenò
2013-05-12 15:02   ` [gentoo-dev] " Duncan
2013-05-12 13:15 ` Ulrich Mueller
2013-05-12 15:04   ` Markos Chandras
2013-05-12 15:17     ` Peter Stuge
2013-05-12 15:48     ` Ulrich Mueller
2013-05-12 15:54       ` Markos Chandras
2013-05-12 16:08         ` Rich Freeman
2013-05-12 16:12           ` Michael Palimaka
2013-05-14 15:44           ` William Hubbs
2013-05-14 17:51             ` Rich Freeman
2013-05-12 16:55         ` Ulrich Mueller
2013-05-12 16:04       ` Mike Gilbert
2013-05-12 17:20     ` Peter Stuge
2013-05-12 17:32       ` Michael Palimaka
2013-05-12 18:24         ` Peter Stuge
2013-05-12 18:31           ` Michael Palimaka
2013-05-12 22:12           ` Alexander Berntsen
2013-05-12 22:21             ` Peter Stuge
2013-05-12 22:24               ` Alexander Berntsen
2013-05-12 22:37                 ` Peter Stuge
2013-05-13  7:09                   ` Alexander Berntsen
2013-05-12 22:38                 ` W. Trevor King
2013-05-13  6:32                 ` Ralph Sennhauser
2013-05-13  7:07                   ` Alexander Berntsen
2013-05-13  7:40                     ` Ralph Sennhauser
2013-05-13  7:47                       ` Alexander Berntsen
2013-05-13 13:28                   ` Ciaran McCreesh
2013-05-14 15:55               ` William Hubbs
2013-05-13 12:38             ` Greg KH
2013-05-13 12:42               ` Alexander Berntsen [this message]
2013-05-13 21:59                 ` Duncan
2013-05-12 17:33       ` Theo Chatzimichos
2013-05-12 18:22         ` Peter Stuge
2013-05-12 19:18       ` [gentoo-dev] GitLab Feature-Set / Was: " sascha-ml
2013-05-14 13:59         ` Rich Freeman
2013-05-14 14:19           ` Peter Stuge
2013-05-14 14:40             ` Rich Freeman
2013-05-13  3:38     ` [gentoo-dev] " Arun Raghavan
2013-05-12 15:13   ` Richard Yao
2013-05-12 15:38     ` Ulrich Mueller

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=5190DFD2.5000201@plaimi.net \
    --to=alexander@plaimi.net \
    --cc=gentoo-dev@lists.gentoo.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