how to correct/patch documentation?

John W. Eaton jwe at bevo.che.wisc.edu
Mon Feb 18 21:23:04 CST 2008


On 18-Feb-2008, Ben Abbott wrote:

| Two more questions.
| 
| (1) I have a few lingering patches what were submitted by email, but  
| not yet committed. Do you prefer them to be resubmitted? Do you prefer  
| emails with patches to have something like "[PATCH]" in the subject  
| line? ... I've not been consistent regarding that, which can't be a  
| good thing.

If you don't mind doing that, it would help.

| (2) CVS was a hassle when new files were to be added to the project. I  
| haven't yet tried, or even looked ... but will that process run  
| smoother now?

Yes, because you can "hg add" files to your clone of the archive.
Then when you export changes, the changeset will include the new file
and it should import cleanly.

If you rename files in the repository, then I think you need to use
the -g option with export, otherwise the diffs will just show that one
file has been added and one file has been removed.  If you use -g,
then the diff includes the rename information, so hg import can know
about the move instead of just adding a file and removing another.

jwe


More information about the Bug-octave mailing list