[Carpet] [Carpet-darcs] Add an example of "manual" scheduling, based on the problem I (and Jonathan) had arose on developers at lists.carpetcode.org as "Carpet scheduling question".

[Luca Baiotti]

>> By the way, it would be nice if it were possible in darcs to unpull in
>> an easy way all the patches pushed after a given date. This would also
>> make it easier to find which patch broke a particular testsuite.
> 
> 
> Darcs does not remember the date at which a patch was pushed; it only  
> remembers the date at which a patch was recorded.  This is because  
> repositories can be copied in many ways, and also because of one  
> important property of darcs: the order in which patches are pushed or  
> pulled does not matter at all; the result is always the same.  The  
> patches in a repository are ordered by date-added, but there are some  
> repository actions that reorder patches.  

darcs could register independently the time of pushing, just for 
debugging-by-humans purposes, though. It would be convenient, as said. 
Anyway, we are not darcs developers and this is not the place for such 
discussions, actually. Sorry.

> You can try
> 
>     darcs unpull --last=10

Yes, this seems the quickest possible, but still one has to count how 
many patches are there before a given one.

> and see whether this does what you expect.  There is also an "-- 
> interactive" option.
> 
> Having said that, you can look into the directory _darcs/patches to  see 
> the individual patches, and the time stamps on the files tell you  when 
> a patch was pushed.  "ls -ltr" lists them sorted by date, 

This date is the date of when I pulled the patch, rather than of when it 
was pushed. So, in particular in the case of a fresh pull, this is useless.


Luca.