Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Sascha Silbe <sascha-ml-reply-to-2010-2@silbe.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] alternative for sup-sync option --restored?
Date: Sun, 22 Aug 2010 15:40:45 +0200	[thread overview]
Message-ID: <1282484196-sup-4382@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <1281085361-sup-7888@xo15-sascha.sascha.silbe.org>


[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]

Excerpts from Sascha Silbe's message of Fri Aug 06 11:13:42 +0200 2010:

> I'm reading and writing my mails on both my desktop (which has the entire archive, totalling ~ 16GB) and my laptop (recent mails and partial archive, ~ 1-2GB).
> Up to now I used sup-dump and sup-sync --restored to synchronize the two (every time I switched between them, since it's a full dump as opposed to a log file or diff).
> After merging the latest changes (including a full dump + restore for index upgrade, taking about 33 hours), the --restored option to sup-sync is gone (and without it sup-sync doesn't do anything useful). How do I go about "merging" the changes done on the other system now?

Any suggestion? This is preventing me from updating to git master and rebasing my outstanding patches.

Sascha

--
http://sascha.silbe.org/
http://www.infra-silbe.de/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2010-08-22 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  9:13 Sascha Silbe
2010-08-22 13:40 ` Sascha Silbe [this message]
2011-01-19 13:52 ` [sup-devel] [PATCH] add sup-import-dump: import message state in sup-dump format Sascha Silbe
2011-01-20  4:13   ` Rich Lane
2011-01-20 15:28   ` Nicolas Pouillard
2011-01-21 12:36     ` Sascha Silbe

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=1282484196-sup-4382@xo15-sascha.sascha.silbe.org \
    --to=sascha-ml-reply-to-2010-2@silbe.org \
    --cc=sup-devel@rubyforge.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