From: Karel Zak <kzak@redhat.com>
To: Tzafrir Cohen <tzafrir@cohens.org.il>
Cc: util-linux@vger.kernel.org
Subject: Re: sfdisk: dump format changed in 2.26
Date: Tue, 24 Nov 2015 16:33:03 +0100 [thread overview]
Message-ID: <20151124153300.GD4955@ws.net.home> (raw)
In-Reply-To: <20151119092827.GJ23928@lemon.cohens.org.il>
On Thu, Nov 19, 2015 at 10:28:28AM +0100, Tzafrir Cohen wrote:
> New versions seem to be able to use old dumps.
This has been the most important :-)
> A simple script I use here to convert new format to old:
>
> sed \
> -e 's/type=/Id=/' \
> -e '/^label:/d' \
> -e '/^label-id:/d' \
> -e '/^device:/d' \
> #
>
> From what I could see, "Id" was changed to "type" in the body and
> various extra header lines were added. Al of those changes make the dump
> file unreadable by older versions.
>
> Is there any intention to support some sort of compatibility through an
> extra option?
I'm not sure if we really need (and want) to provide compatibility in
this way. Maybe we can add the sed command to the man page.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2015-11-24 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:28 sfdisk: dump format changed in 2.26 Tzafrir Cohen
2015-11-24 15:33 ` Karel Zak [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=20151124153300.GD4955@ws.net.home \
--to=kzak@redhat.com \
--cc=tzafrir@cohens.org.il \
--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