[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 baiotti at aei.mpg.de
Fri Sep 1 11:45:05 CEST 2006


Hi Erik.

>> darcs could register independently the time of pushing, just for
>> debugging-by-humans purposes, though. It would be convenient, as said.
> 
> You probably assume that there is exactly one repository, and darcs  
> should record when a patch is pushed to it.  This is not the case.   
> There can be many independent repositories, and none is more  important 
> than the others.

Yes, I assumed that. But I believe that for the users and the occasional 
developers, there exist effectively exactly one repository, that is 
darcs at cvs.carpetcode.org:/home/darcs/carpet and they usually want their 
local copy to be identical to (one version of) that repository.

But the darcs system is apparently better for the full time developers.

> For example, I have two repositories on my notebook, one for the  
> original version, and one to play around.  That means that a patch  has 
> already been pushed twice when you see it on cvs.carpetcode.org.   
> Additionally, there is no difference between pushing and pulling  
> (except that you give one command in the source, the other in the  
> destination repository).  That is, you could also push a patch from  
> cvs.carpetcode.org into your local darcs repository instead of  pulling it.
> 
> It is therefore not possible to record the time and date of "the"  
> push.  Darcs remembers when a patch was recorded originally, and the  
> order in which they arrived in your local repository.  How and when  the 
> patch travelled in between (push, pull, email, download from a  web 
> page, etc.) is not recorded.
> 
> You can, for all practical purposes, act as if your local repository  
> was the most important one, and use the order of the patches in there.

I have strated doing the following, if someone else is interested.

I put the Carpet darcs pull in a CVS repository (paying attention not to 
import in CVS the _darcs directory, which gives problems and is 
unnecessary) and I plan to have nightly pulls from 
darcs at cvs.carpetcode.org:/home/darcs/carpet and commits to the CVS 
repository. Comments and suggestions are welcome.


Ciao,

Luca.





More information about the developers mailing list