Re: [Monotone-devel] ikiwiki and monotone

[Daniel Carosone]

On Wed, Oct 11, 2006 at 12:46:54AM -0700, Nathaniel Smith wrote:
> To avoid this, we should add an "automate get_birth_revision" command,
> or something like that.  We recently added "get_corresponding_path"
> and "get_content_changed" commands to expose similar bits of roster
> information

I figured that get_content_changed | toposort would be the way to get
this, absent a specific command.

> The bit about having to pick a date if there are several date certs
> (or potentially fail if there is no date cert) is unfortunate, but
> basically unavoidable.  What you get is what monotone stores, if you
> want something else that monotone doesn't store, then you have to
> figure out what the best way to approximate it is in your particular
> situation.  Since monotone doesn't know your situation, it can't
> really tell what the best way to guess would be.

A possible future alternative is the date the revision was added to
the local db, if we end up storing that as suggested in the TimeStamps
page.

--
Dan.

pgpAt8lEty49r.pgp
Description: PGP signature