public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentincj@iksaif.net>
Cc: linux-mtd@lists.infradead.org, vapier.adi@gmail.com
Subject: Re: [PATCH 1/2] mkfs.ubifs: UBI I/O Library
Date: Fri, 08 May 2009 11:49:23 +0300	[thread overview]
Message-ID: <1241772563.27996.81.camel@localhost.localdomain> (raw)
In-Reply-To: <1241691709-17624-2-git-send-email-corentincj@iksaif.net>

Hi,

thanks for patches. Could you please avoid synchronizing 
include/mtd/ubi-user.h for now? There is nothing new there
except of this insane s/int32_t/__s32/ type change, right?

On Thu, 2009-05-07 at 12:21 +0200, Corentin Chary wrote:
>  include/mtd/ubi-user.h    |   72 ++--
>  include/ubi.h             |  192 +++++++++
>  mkfs.ubifs/libubiio.c     |  936 +++++++++++++++++++++++++++++++++++++++++++++
>  mkfs.ubifs/libubiio.h     |   47 +++
>  mkfs.ubifs/libubiio_int.h |  187 +++++++++
>  5 files changed, 1399 insertions(+), 35 deletions(-)
>  create mode 100644 include/ubi.h
>  create mode 100644 mkfs.ubifs/libubiio.c
>  create mode 100644 mkfs.ubifs/libubiio.h
>  create mode 100644 mkfs.ubifs/libubiio_int.h

What is the point of making a second copy of libubi?
AFAICS, libubio is libubi + other stuff, right?
Why not to just improve libubi instead of having yet
another copy? How much sense does it make?

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  parent reply	other threads:[~2009-05-08  8:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 10:21 [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 10:21 ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Corentin Chary
2009-05-07 10:21   ` [PATCH 2/2] mkfs.ubifs: format directly ubi volume using libubiio Corentin Chary
2009-05-08  8:49   ` Artem Bityutskiy [this message]
2009-05-08 12:07     ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Corentin Chary
2009-05-08 12:20       ` Artem Bityutskiy
2009-05-08 13:58         ` Corentin Chary
2009-05-08 14:06           ` Artem Bityutskiy
2009-05-08 14:14         ` Artem Bityutskiy
2009-05-08 14:59           ` Corentin Chary
2009-05-08 18:58             ` Mike Frysinger
2009-05-08 19:41               ` Corentin Chary
2009-05-08 20:25                 ` Mike Frysinger
2009-05-08 20:32                   ` Corentin Chary
2009-05-08 20:36                     ` Mike Frysinger
2009-05-07 11:59 ` [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 12:57 ` Josh Boyer
2009-05-07 13:29   ` Corentin Chary

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=1241772563.27996.81.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=corentincj@iksaif.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier.adi@gmail.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