Re: [Monotone-devel] Exclude fiiles from commit

[Georg Lohrer]

Am Mittwoch, 30. März 2005 13:21 schrieb address@hidden:
> Hi Nat et al
>
> I was just thinking about a common problem which I had in Clearcase -
> there is no way to 'locally edit' a file without checking it out(*),
> and developers often checked these files in by mistake. For example a
> local file which contains a complex set of parameters, some of which
> need to be edited to parameterise tests etc, or a file in which the
> developer wants to put a quick hack during testing.

In ClearCase you are obliged to check in your necessary files and then 
use branches for your own adaptions, even small ones. After your 
successfull operation you can remove the files-versions on the branch 
with "rmbranch". Or you let the branch as it is, nobody will hassle 
about this.
You can prevent unauthorized checkouts of the original version by settin 
the permissions accordingly (cleartool protect).
The complete unability to checkout or branch VOB-objects could be done 
with the 'lock'.

As I understand you want to have write-access to one file without 
changing it in the repository. 
From my point of view, you cannot not have the write permission and 
simultaneously the assurance of the system that the changed file won't 
be commited during commit-phase.

The CVS '.cvsignore' file goes somewhat in that direction but prevents 
from being noticed at all.

There seems to be two ways of handle this situation:

1) The developers care about their own fingerwork and deal with some 
circumstances like branches
2) Your build-environment have to be changed to not use the origin place 
of the source, but use something like a specially prepared build-place 
(build-VOB, build-directory, etc.). You will have an intermediate step 
in this scenario there you can change all you need.

Ciao, Georg

-- 
Georg Lohrer
GnuPGP-Key available on WebSite http://www.croxx.de