From: Petr Uzel <petr.uzel@suse.cz>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] libuuid,uuidd: move read_all to include/readall.h
Date: Mon, 14 May 2012 11:53:15 +0200 [thread overview]
Message-ID: <20120514095315.GB4335@foxbat.suse.cz> (raw)
In-Reply-To: <20120514094601.GC16926@x2.net.home>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On Mon, May 14, 2012 at 11:46:01AM +0200, Karel Zak wrote:
> On Sun, May 13, 2012 at 09:37:56AM +0200, Petr Uzel wrote:
> > include/Makefile.am | 1 +
> > include/readall.h | 33 +++++++++++++++++++++++++++++++++
> > libuuid/src/gen_uuid.c | 26 +-------------------------
> > misc-utils/uuidd.c | 25 +------------------------
> > 4 files changed, 36 insertions(+), 49 deletions(-)
> > create mode 100644 include/readall.h
>
> Good idea, but do we really need writeall.h and readall.h ? ;-) What
> about to merge both files? (all-io.h ?)
Sounds good, I'll merge them.
Thanks,
Petr
--
Petr Uzel
IRC: ptr_uzl @ freenode
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-05-14 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 7:37 [PATCH] libuuid,uuidd: move read_all to include/readall.h Petr Uzel
2012-05-14 9:46 ` Karel Zak
2012-05-14 9:53 ` Petr Uzel [this message]
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=20120514095315.GB4335@foxbat.suse.cz \
--to=petr.uzel@suse.cz \
--cc=kzak@redhat.com \
--cc=util-linux@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