From: Valdis.Kletnieks@vt.edu
To: Dominic Hamon <dominic@google.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
web10g-user@web10g.org
Subject: Re: [Web10g-user] Web10g TCP statistics patch - mainlining into kernel?
Date: Fri, 25 Jan 2013 13:57:57 -0500 [thread overview]
Message-ID: <20357.1359140277@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 25 Jan 2013 10:38:59 -0800." <CAO1dsSdQJDKZ+zzCaLgge9wqiNaJFzPWWBLjRkMEswLVOOd0qA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Fri, 25 Jan 2013 10:38:59 -0800, Dominic Hamon said:
> Hello Valdis
>
> I actually just finished patching a fork from the kernel github repo here:
> https://github.com/dominic-mlab/linux with a view to pushing it up. I
> haven't pushed a patch upstream before, so any guidance is welcome.
A quick browse over that git repo looks like it's unfortunately a tad
busticated - you've apparently got development on the 'master' branch, instead
of starting a separate branch. This effectively means that it can't be easily
pulled upstream. Fortunately, you only have one commit against it so
far, so you can probably recover by rejecting that commit so you're back
to a Linus tree, and then create a branch and do subsequent development there.
Question for the netdev people - you prefer pull requests based off
a Linus tree, or linux-next, davem/(net,net-next), or some other tree?
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2013-01-25 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:31 Valdis Kletnieks
[not found] ` <CAO1dsSdQJDKZ+zzCaLgge9wqiNaJFzPWWBLjRkMEswLVOOd0qA@mail.gmail.com>
2013-01-25 18:57 ` Valdis.Kletnieks [this message]
2013-01-25 19:34 ` [Web10g-user] " rapier
2013-01-25 19:56 ` Valdis.Kletnieks
2013-01-25 20:08 ` rapier
2013-01-25 23:34 ` Tom Herbert
2013-01-29 17:49 ` Ben Hutchings
2013-01-29 18:52 ` David Miller
2013-01-29 19:34 ` [Web10g-user] " rapier
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=20357.1359140277@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=dominic@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=web10g-user@web10g.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
all inboxes | Powered by JetHome®