From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] 483dce: Refeshed quagga patch set for the RE branch
Date: Fri, 10 Feb 2012 07:57:17 -0800 [thread overview]
Message-ID: <4f353e5d4a5_254c1058aec9083d@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: 483dcec42cb96647223a529569fe72934970cc6a
https://github.com/dtaht/ceropackages/commit/483dcec42cb96647223a529569fe72934970cc6a
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-10 (Fri, 10 Feb 2012)
Changed paths:
R net/quagga/patches/110-fix_ipctl_forwarding.patch
R net/quagga/patches/120-quagga_manet.patch
M net/quagga/patches/130-fix_cpp.patch
R net/quagga/patches/140-holdtimer-set.patch
M net/quagga/patches/150-no-cross-fs-link.patch
M net/quagga/patches/160-pgbgp.patch
R net/quagga/patches/161-pgbgp-addon.patch
M net/quagga/patches/170-use-supported-pagers.patch
Log Message:
-----------
Refeshed quagga patch set for the RE branch
Rather than understand them, I deleted the manet patches
which at least theoretically supported batman and olsr.
I kept the 'pretty good bgp' patches, but am not
in a position to test.
Several of the remaining patches can be pushed into the quagga-RE branch
after a bit of testing.
Commit: a7230e0d6ba257d48bc3ca87129dbef3fa2e1739
https://github.com/dtaht/ceropackages/commit/a7230e0d6ba257d48bc3ca87129dbef3fa2e1739
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-10 (Fri, 10 Feb 2012)
Changed paths:
M net/quagga/Makefile
Log Message:
-----------
Pull quagga from the last known decent commit
Compare: https://github.com/dtaht/ceropackages/compare/abe03d3...a7230e0
reply other threads:[~2012-02-10 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f353e5d4a5_254c1058aec9083d@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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