All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: dedekind1@gmail.com
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH v3 0/7] prepare new nanddump options, defaults
Date: Sun, 26 Jun 2011 09:15:35 +0200	[thread overview]
Message-ID: <87r56h6p2g.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1308946822.13493.36.camel@koala> (Artem Bityutskiy's message of "Fri, 24 Jun 2011 23:20:17 +0300")

>>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:

Hi,

 >> i dont think anyone has scripts parsing these things.  i say let's
 >> just lock them all to the mtd release and forget about it.

 Artem> Let's ask CC Peter who is packaging mtd-utils just in
 Artem> case. Peter, will you suffer if mtd-utils' version all suddenly
 Artem> become 1.4.6? Also, will you suffer if we switch to 2.0 or 3.0 -
 Artem> 2 numbers instead of 3?

No, the version number doesn't matter as long as it increases and
release tarballs are made.

Thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-06-26  7:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 15:46 [PATCH v2 0/7] new nanddump defaults Brian Norris
2011-06-21 15:46 ` [PATCH v2 1/7] nanddump: add --bb=METHOD option Brian Norris
2011-06-21 15:46 ` [PATCH v2 2/7] nanddump: remove --skipbad, leaving --bb=skipbad Brian Norris
2011-06-21 15:46 ` [PATCH v2 3/7] nanddump: deprecation messages for old BB options Brian Norris
2011-06-21 19:38   ` Mike Frysinger
2011-06-21 15:46 ` [PATCH v2 4/7] nanddump: warn about new default BB handling Brian Norris
2011-06-21 19:37   ` Mike Frysinger
2011-06-21 15:46 ` [PATCH v2 5/7] feature-removal-schedule: describe nanddump changes Brian Norris
2011-06-21 15:46 ` [PATCH v2 6/7] nanddump: add --oob option Brian Norris
2011-06-21 15:46 ` [PATCH v2 7/7] nanddump: document, warn about future default --omitoob Brian Norris
2011-06-21 19:39   ` Mike Frysinger
2011-06-21 19:40 ` [PATCH v2 0/7] new nanddump defaults Mike Frysinger
2011-06-21 22:36   ` Brian Norris
2011-06-22 16:49     ` [PATCH v3 0/7] prepare new nanddump options, defaults Brian Norris
2011-06-23 15:02       ` Artem Bityutskiy
2011-06-23 15:04         ` Artem Bityutskiy
2011-06-23 15:52           ` Mike Frysinger
2011-06-23 23:00             ` Brian Norris
2011-06-23 23:14               ` Mike Frysinger
2011-06-23 23:27                 ` Brian Norris
2011-06-23 23:36                   ` Mike Frysinger
2011-06-23 23:40                     ` Brian Norris
2011-06-23 23:45                       ` Mike Frysinger
2011-06-23 23:48                         ` Brian Norris
2011-06-24 20:20                 ` Artem Bityutskiy
2011-06-26  7:15                   ` Peter Korsgaard [this message]
2011-06-24 17:37               ` Brian Norris
2011-06-24 18:28                 ` Mike Frysinger
2011-06-24 19:21                   ` Artem Bityutskiy
2011-06-24 20:11                 ` Artem Bityutskiy
2011-06-24 20:15               ` Artem Bityutskiy
2011-06-24 19:38             ` Artem Bityutskiy
2011-06-22 16:49     ` [PATCH v3 1/7] nanddump: add --bb=METHOD option Brian Norris
2011-06-22 16:49     ` [PATCH v3 2/7] nanddump: remove --skipbad, leaving --bb=skipbad Brian Norris
2011-06-22 16:49     ` [PATCH v3 3/7] nanddump: update help message for BB method changes Brian Norris
2011-06-22 16:49     ` [PATCH v3 4/7] nanddump: warn about new default BB handling Brian Norris
2011-06-22 16:49     ` [PATCH v3 5/7] feature-removal-schedule: describe nanddump changes Brian Norris
2011-06-22 16:49     ` [PATCH v3 6/7] nanddump: add --oob option Brian Norris
2011-06-22 16:49     ` [PATCH v3 7/7] nanddump: document, warn about future default --omitoob Brian Norris

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=87r56h6p2g.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.