From: Stephen Hemminger <stephen@networkplumber.org>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: netdev@vger.kernel.org
Subject: Re: Problems in tc-matchall.8, tc-sample.8
Date: Tue, 12 Jun 2018 17:24:39 -0700 [thread overview]
Message-ID: <20180612172439.6416b4e7@xeon-e3> (raw)
In-Reply-To: <20180612234103.GB14546@thyrsus.com>
On Tue, 12 Jun 2018 19:41:03 -0400
"Eric S. Raymond" <esr@thyrsus.com> wrote:
> Stephen Hemminger <stephen@networkplumber.org>:
> > On Tue, 12 Jun 2018 18:00:03 -0400
> > "Eric S. Raymond" <esr@thyrsus.com> wrote:
> >
> > > Stephen Hemminger <stephen@networkplumber.org>:
> > > > Please resubmit as real patch with signed-off-by
> > >
> > > I would like to follow your intructions, but that description leaves me
> > > not quite certain what you want. A git format-patch thing? If so, what
> > > git url should I clone from?
> >
> > iproute patches are handled the same as the Linux kernel.
> > Please submit patches to the netdev@vger.kernel.org with the same kind
> > of diff format (and signed-off-by) as the kernel.
> >
> > Like the kernel, patches which are pure bug fixes go to the master
> > branch, and patches with new functionality are handled with the iproute2-next repository.
>
> Then I should bugfix against this repository?
>
> https://github.com/shemminger/iproute2
The upstream repositories for master and net-next branch are now
split. Master branch is at:
git://git.kernel.org/pub/scm/network/iproute2/iproute2.gti
and patches for next release are in (master branch):
git://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git
Github is an out of date clone (like all the kernels on there).
next prev parent reply other threads:[~2018-06-13 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180612191614.916303A4F8E@snark.thyrsus.com>
2018-06-12 21:17 ` Problems in tc-matchall.8, tc-sample.8 Stephen Hemminger
2018-06-12 22:00 ` Eric S. Raymond
2018-06-12 22:33 ` Stephen Hemminger
2018-06-12 23:41 ` Eric S. Raymond
2018-06-13 0:24 ` Stephen Hemminger [this message]
2018-06-13 1:12 ` Eric S. Raymond
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=20180612172439.6416b4e7@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=esr@thyrsus.com \
--cc=netdev@vger.kernel.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).