[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".

[Erik Schnetter]

On Sep 4, 2006, at 04:27:56, Luca Baiotti wrote:

> Another useful thing could be to separate CarpetWeb in a different
> repository, so that the repository for the code contain a lot fewer  
> patches.

I view web pages like documentation.  In fact, many people consult  
web pages much more willingly than looking at pdf files.  I would  
like to keep documentation bundled with the code.

The command "darcs changes Carpet" lists only those patches which  
affect the directory "Carpet" or one of its subdirectories.  That  
helps you filter out unwanted patches.

Most patches to the web pages should start with the prefix  
"CarpetWeb:"; that should make it possible to ignore them semi- 
automatically.

Modern versioning systems (i.e., about everything more modern than  
CVS) keep track of patches not per file, but instead for the whole  
repository.  Each commit leads to a new version.  That means that  
there are many versions created, and many patches to be considered.   
I'm afraid that's not going to go away.  Instead, one would use  
automatic tools to process patches, or a graphical user interface.   
Maybe there is a plugin for Eclipse?

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : /archives/developers/attachments/20060904/8373ad47/attachment.pgp