patch queues and having a patch own a file

[Tod Olson]

I'm using patch queues on a project, and am trying to figure out how to have a patch own a file.  The goal would be that a qpush of the patch cause the file to be created, and a qpop of the patch would remove the file.

For example: I've added a config file to someone else's code.  It seemed like "hg add" was the only way to get the patch queue to be aware of the new file, but now every time I run "hg qpop -a", the config file must be removed manually or reapplying the patches will fail.

Another example is adding an image file for skinning purposes. I'd like that image file to be part of a patch, so it it is picked up with an hg push of the patches.

I've spent a little time in the archives look for solutions to this problem, but have not had much luck.  Maybe just not the right search terms.

How do others address this business of associating a new file with a patch?

-Tod

Tod Olson <tod at uchicago.edu>
Systems Librarian
University of Chicago Library