From: maximilian attems <max@stro.at>
To: klibc@zytor.com, dash@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.hengli.com.au>
Subject: [RFC] klibc dash merge
Date: Sat, 4 Jun 2011 07:00:05 +0000 [thread overview]
Message-ID: <20110604070005.GE22026@vostochny.stro.at> (raw)
Hello,
Since klibc dash last merge is a bit dated yesterday I resyncronised
the dash in klibc repo from dc2bc17c7bbe3188cfb0c695dc472b39bcf0b27a
up to ec2c84d3c4dba4b74440d72bdd1de416a9acd2a9 commit.
Please test it:
git://git.kernel.org/pub/scm/libs/klibc/klibc-queue.git
http://git.kernel.org/?p=libs/klibc/klibc-queue.git;a=shortlog
Without objections this will land in klibc-1.5.23.
It got easier (less error prone handeting) since newer git got more
features. Only some commits needed a manual merge fixup.
The end result runs fine for an initramfs-tools boot.
Nevertheless please give me hints if I shouldn't merge at this
point of history and wait for some upcoming push (eventual v0.5.7)?
Thank you
--
maks
P.S. will send soonest the DEBUG compile fix.
P.P.S need to send in 2 klibc dash features to the main repo from hpa.
next reply other threads:[~2011-06-04 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 7:00 maximilian attems [this message]
2011-06-09 8:30 ` [klibc] [RFC] klibc dash merge maximilian attems
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=20110604070005.GE22026@vostochny.stro.at \
--to=max@stro.at \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.hengli.com.au \
--cc=klibc@zytor.com \
/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).