Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Heidelberger <david.heidelberger@ixit.cz>
To: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: iputils: maintanace fork
Date: Tue, 22 Apr 2014 14:07:41 +0200 [thread overview]
Message-ID: <3d2e1f5d3adfab1bae799b8a557e87b8@ixit.cz> (raw)
Hello,
because latest iputils release (and also last commit in git repo.)
happened more than year ago and bugs of iputils differs on every
distrubution, because of different number of used patches I decided to
work on iputils to get all important patches together.
Project can be found on github [1], build bot on travis-ci [2].
For Yoshfuji Hideaki, first I want to apologize for starting this
without notifying you. I though you're not interested anymore, but some
people pointed me that you response to emails, only it takes more time.
If you're still interested in maintaining iputils, I'm ready to give you
full access to github and travis-ci :)
For people with difficulties: report them to github issues, to keep
track of them.
For people with patches: please rebase them against lastest work in git
repository and submit them as pull request (this ensure automatic build
test). Also please try attach some command to test correctness of your
changes.
For package maintainers: At moment writing there is RELEASE s20140420 on
github, with integrated musl-libc fixes (mostly headers) and most of
Debian and Gentoo patches. If you want ensure that quality of code is
high enough, read git changelog [3] and travis-ci build history [2] with
gcc-4.8 and clang.
Thank you for reading
David Heidelberger (okias)
[1] https://github.com/iputils/iputils
[2] https://travis-ci.org/iputils/iputils
[3] https://github.com/iputils/iputils/commits/master
[4] http://www.musl-libc.org/
reply other threads:[~2014-04-22 11:09 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=3d2e1f5d3adfab1bae799b8a557e87b8@ixit.cz \
--to=david.heidelberger@ixit.cz \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
--subject='Re: iputils: maintanace fork' \
/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
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).