unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Revised dump-restore patches
Date: Sun, 18 Dec 2011 12:51:56 -0800	[thread overview]
Message-ID: <87wr9tob6b.fsf@servo.finestructure.net> (raw)
In-Reply-To: <1324214111-32079-1-git-send-email-david@tethera.net>

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

On Sun, 18 Dec 2011 09:15:02 -0400, David Bremner <david@tethera.net> wrote:
> I left the default dump format as "sup" (old style) in this round. I'm
> leary of breaking people's scripts, so my current proposal is
> deprecate the sup format (as default) for a release or two.

It seems to me that as long as restore can detect what format the dump
file is in, it shouldn't matter what the default dump format is, right?
If someone makes a new dump in the new format, they'll presumably also
be restoring with the new code that supports that format as well.  I'm
having a hard time imagining a situation where moving to a new
fully-supported default dump format would break anything.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2011-12-18 20:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <id:87sjkmuck7.fsf@gmail.com>
2011-12-18 13:15 ` Revised dump-restore patches David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 1/9] hex-escape: (en|de)code strings to/from restricted character set David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 2/9] test/hex-xcode: new test binary David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 3/9] test/hex-escaping: new test for hex escaping routines David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 4/9] notmuch-dump: add --format=(notmuch|sup) David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 5/9] test: add test for dump --format=notmuch David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 6/9] notmuch-restore: add --format=notmuch support David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 7/9] test: second set of dump/restore --format=notmuch tests David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 8/9] notmuch-restore: auto detect format of backup David Bremner
2011-12-18 13:15   ` [PATCH Draft 2 9/9] test: add tests for restore --auto David Bremner
2011-12-18 20:51   ` Jameson Graef Rollins [this message]
2011-12-18 22:09     ` Revised dump-restore patches David Bremner
2012-01-15  1:40       ` New dump/restore format David Bremner
2012-01-15  1:40         ` [PATCH v3 01/10] hex-escape: (en|de)code strings to/from restricted character set David Bremner
2012-01-15  1:40         ` [PATCH v3 02/10] test/hex-xcode: new test binary David Bremner
2012-01-15  1:40         ` [PATCH v3 03/10] test/hex-escaping: new test for hex escaping routines David Bremner
2012-01-15  1:40         ` [PATCH v3 04/10] notmuch-dump: add --format=(notmuch|sup) David Bremner
2012-01-15 20:35           ` Austin Clements
2012-01-15 23:40             ` David Bremner
2012-01-15  1:40         ` [PATCH v3 05/10] test: add test for dump --format=notmuch David Bremner
2012-01-15  1:40         ` [PATCH v3 06/10] notmuch-restore: add 'notmuch format' support, auto detect David Bremner
2012-01-15  1:40         ` [PATCH v3 07/10] test: second set of dump/restore --format=notmuch tests David Bremner
2012-01-15  1:40         ` [PATCH v3 08/10] notmuch-{dump, restore}.1: document new format options David Bremner
2012-01-15  1:40         ` [PATCH v3 09/10] random-dump.c: new test-binary to generate dump files David Bremner
2012-01-15  8:05           ` Jani Nikula
2012-01-15 13:44             ` David Bremner
2012-02-05  1:04           ` Mark Walters
2012-01-15  1:40         ` [PATCH v3 10/10] test: new random message-id and tags dump/restore test David Bremner

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wr9tob6b.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).