There should be a way to record the time a patch is merged (and log further 
unmerges and remerges) into a repository. Repositories can be identified by a 
UUID, if not already. This would allow one to see exactly what a repository 
looked like at a certain time.

While I see that this could useful in some case, it also strikes me as difficult
and unnecessary. 

There is a simple workaround for getting logging when some patches are pulled:

Before pulling, do this: 

darcs tag prepull

You have now just indicated that you are "just about to pull" at a particular
moment, merging the patches that follow until the next prepull tag. 

Darcs does not "remerge" because it has better accounting practices. An
"unmerge" log could be creating another tag just before rolling back. 

This system could even be automated by use of the darcs hook system. 

I vote for resolving this ticket as "wont-fix".

I agree.  We've already got one mechanism, tags, for recording the state of a
repository, and I see no reason to add another.  We could potentially add an
auto-tag option to pull/apply, but I'm not sure anyone would actually want to
use that.

Why don't you care about keeping the history of the repository? That's the 
primary purpose of recording all this in the first place!

Luke-Jr wrote:
> 
> Why don't you care about keeping the history of the repository? That's the 
> primary purpose of recording all this in the first place!

Luke,

The tag mechanism does record the state of the repository and provides a 
specific timestamp.

Darcs is open source and you are welcome to implement the feature in 
your own copy, or hire or persuade any one else to add the feature. If 
it seems popular or there is more demand from this feature, it could 
always be re-considered adding it to the mainline release.

    Mark

On Jan 30, 2008 2:16 PM, Mark Stosberg <bugs@darcs.net> wrote:
> > Why don't you care about keeping the history of the repository? That's the
> > primary purpose of recording all this in the first place!

No, it's not.  The primary purpose of darcs is to track of changes,
not a history of repository states.  If you want the latter, you
should either use a different tool that is designed for this purpose
(e.g. git), or recognize that since you're using darcs to do something
it's not designed for, it won't always work as smoothly as you might
like.

David

On Wednesday 30 January 2008, David Roundy wrote:
> On Jan 30, 2008 2:16 PM, Mark Stosberg <bugs@darcs.net> wrote:
> > > Why don't you care about keeping the history of the repository? That's
> > > the primary purpose of recording all this in the first place!
>
> No, it's not.  The primary purpose of darcs is to track of changes,
> not a history of repository states.

Merging patches is a change.

> Merging patches is a change.

So create a tag before or after you merge, and automate that if you want 
to.

   Mark

On Jan 30, 2008 2:52 PM, Luke-Jr <bugs@darcs.net> wrote:
> Merging patches is a change.

If you want to use git, use git.

David