On Wed, Jun 4, 2014 at 11:15 AM, Stephan Beal <sgb...@googlemail.com> wrote: > On Wed, Jun 4, 2014 at 6:03 PM, Nico Williams <n...@cryptonector.com> wrote: >> On Wed, Jun 4, 2014 at 9:07 AM, Stephan Beal <sgb...@googlemail.com> >> wrote: >> > Bookmarks. That's a nice idea, actually. Added to my TODO list. > > i was thinking more generically: > > f bookmark add blah trunk > f bookmark add 'oops!' deadbeefabcdef0123 > > f bookmark ls > [blah] = trunk > [oops!] = deadbeefabcdef0123 > > f co bk:oops > f merge bk:trunk > > i.e. a system with which to assign non-version-tracked aliases to arbitrary > other symbols which we already know how to resolve. They needn't be > push/pull'able, but it might be nice to be able to. We already have > precedents for "special symbols" like bk:NAME, e.g.:
To be truly useful it has to be possible to [selectively] push/pull bookmarks. Strictly speaking, bookmarks needn't be versioned, but it's nice to have something like the git "reflog" to help you recover from accidentally clobbering a bookmark. In effect, bookmarks' history needs to be versioned, because let's face it, the git reflog is an odd bolt-on thing, odder still when you consider that git has a powerful history mechanism. So, yeah, bookmarks should be versioned. Nico -- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
