unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: 20137@debbugs.gnu.org
Subject: bug#20137: number of generation doesn't always rise monotonically
Date: Thu, 19 Mar 2015 09:47:06 +0100	[thread overview]
Message-ID: <871tkl8jcl.fsf@gnu.org> (raw)
In-Reply-To: <87zj7a3udo.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Wed, 18 Mar 2015 21:47:47 +0100")

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>>   2. Upon rollback from P to N, keep all the generations, but use P+1
>>      for the next generation number.  Doesn’t work, because rolling back
>>      from P+1 would bring you back to P instead of N.
>
> Perhaps we can eventually move to an actual tree structure where the
> nodes can be named whatever.

I agree this would be the right thing for a real undo mechanism.

But how useful would it be?  I’ve never been in a situation where
rollback/switch-generation would be insufficient or inappropriate.

I’m concerned that this would add both code and user interface
complexity for mostly hypothetical use cases.  WDYT?

Thanks,
Ludo’.

  parent reply	other threads:[~2015-03-19  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 17:35 bug#20137: number of generation doesn't always rise monotonically Tomáš Čech
2015-03-18 20:36 ` Ludovic Courtès
2015-03-18 20:47   ` Taylan Ulrich Bayırlı/Kammer
2015-03-18 20:52     ` Thompson, David
2015-03-19  8:47     ` Ludovic Courtès [this message]
2015-03-22 22:48     ` Ludovic Courtès
2015-03-22 23:40 ` Tomáš Čech
2015-03-23  9:13   ` Ludovic Courtès
2015-03-23  9:50     ` Tomáš Čech

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=871tkl8jcl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=20137@debbugs.gnu.org \
    --cc=taylanbayirli@gmail.com \
    /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).