unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Rollback problems
Date: Fri, 25 Jan 2013 15:53:09 +0100	[thread overview]
Message-ID: <87ip6ll3fu.fsf@gnu.org> (raw)
In-Reply-To: <87622mhthi.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 24 Jan 2013 21:44:51 -0500")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>>  3. More generally, should the history of generations be linear, or
>>     should it be a DAG like Git commits?
>
> If the latter is the case, then we can probably use a simple tree.  Here
> is a related link: [1].

Right, if we went for a tree, each manifest could carry some sort of a
zipper that would then allow us to know how to go back from there.

>> Regarding (3), it seems that a linear history not only simplifies the
>> implementation, but also the user interface, while covering most
>> practical use cases.
>
> I agree.

Great.  It really seems simpler to use a linear history.

Thanks,
Ludo’.

  parent reply	other threads:[~2013-01-25 14:53 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 [this message]
2013-01-27 17:05         ` Ludovic Courtès
2013-01-28 22:10           ` Andreas Enge
2013-01-28 22:44             ` Ludovic Courtès
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87ip6ll3fu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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://git.savannah.gnu.org/cgit/guix.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).