public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Kevin Lyda <kevin-lVvlXWpnww44d9/VWYMlNA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: github repo questions...
Date: Sun, 2 Oct 2011 18:59:27 -0400	[thread overview]
Message-ID: <201110021859.28320.vapier@gentoo.org> (raw)
In-Reply-To: <CADJ56BS-pa3fQfLFt1inRc7FF3GJUZ-iw0E+MPmW2PLavZvdqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: Text/Plain, Size: 839 bytes --]

On Sunday, October 02, 2011 17:22:56 Kevin Lyda wrote:
> On Sun, Oct 2, 2011 at 21:34, Michael Kerrisk wrote:
> > It's temporary, but it might become permanent. I've yet to look into
> > all that github can offer, and and I'm waiting to see what life on
> > kernel.org is like once everything is reinstated reinstated, it may
> > end up being more comfortable to just stick with github.
> 
> It's certainly easier to submit patches (using pull requests).

imo, all patches should be hitting the mailing list anyways.  and submitting a 
pull request is pretty much just as easy as the git pull request message tells 
the puller where to find it and which branch to pull.

perhaps the github interface makes this a little easier if it gives you a 
button to click, but that doesn't affect the review process otherwise.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2011-10-02 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 11:40 github repo questions Kevin Lyda
     [not found] ` <CADJ56BQm2zw=+LB=ZbXRBzrFYMAdrDa=v2izUqgR2ywwDRUZiw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-02 19:31   ` Mike Frysinger
     [not found]     ` <201110021531.02138.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2011-10-02 20:34       ` Michael Kerrisk
     [not found]         ` <CAKgNAkio2oYn4TQZe8stu+BgS-N3zm30_s4=kPYAeNxzGGxG9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-02 21:22           ` Kevin Lyda
     [not found]             ` <CADJ56BS-pa3fQfLFt1inRc7FF3GJUZ-iw0E+MPmW2PLavZvdqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-02 22:59               ` Mike Frysinger [this message]
     [not found]                 ` <201110021859.28320.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2011-10-03  6:05                   ` Michael Kerrisk

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=201110021859.28320.vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=kevin-lVvlXWpnww44d9/VWYMlNA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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