From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Rollback problems
Date: Mon, 28 Jan 2013 23:44:43 +0100 [thread overview]
Message-ID: <871ud5q65g.fsf@gnu.org> (raw)
In-Reply-To: <201301282310.34473.andreas@enge.fr> (Andreas Enge's message of "Mon, 28 Jan 2013 23:10:34 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> Am Sonntag, 27. Januar 2013 schrieb Ludovic Courtès:
>> ludo@gnu.org (Ludovic Courtès) skribis:
>> > Having agreed on linear history, it seems that (a) the current
>> > behavior is broken because roll-backs don’t actually follow the
>> > history, as illustrated previously, and (b) the generation from which
>> > we are rolling back must be deleted.
>
> It seems to work: I rolled back from 21 to 20, 19, 18, 17; then removed a
> package and am at 18 now. Then removed another package and arrived at 19,
> where the previous 18 and 19 were overwritten.
Good.
> Personally, I would have deleted all (consecutive) generations starting
> with 19 after the first roll-back and additional package removal; now we
> still have pieces of old history lying around, the (old and) current 20 is
> not a successor of the current 19 any more.
Yeah, I wondered about that and ended up with the approach that’s the
easiest in terms of implementation.
Thanks for testing!
Ludo’.
next prev parent reply other threads:[~2013-01-28 22:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:48 Rollback problems Andreas Enge
2013-01-23 22:58 ` Ludovic Courtès
2013-01-23 23:17 ` Andreas Enge
2013-01-24 11:34 ` Ludovic Courtès
2013-01-24 15:33 ` Alex Sassmannshausen
2013-01-24 15:59 ` Ludovic Courtès
2013-01-24 20:52 ` Ludovic Courtès
2013-01-25 2:44 ` Nikita Karetnikov
2013-01-25 13:54 ` Alex Sassmannshausen
2013-01-25 14:48 ` Andreas Enge
2013-01-25 14:53 ` Ludovic Courtès
2013-01-27 17:05 ` Ludovic Courtès
2013-01-28 22:10 ` Andreas Enge
2013-01-28 22:44 ` Ludovic Courtès [this message]
2013-01-25 3:08 ` Nikita Karetnikov
2013-01-27 17:06 ` Ludovic Courtès
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=871ud5q65g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.