Prevent accidental commit of a versioned and localy changed file

Sabin Iacob iacobs at m0n5t3r.info
Mon Jul 7 10:13:57 BST 2008


Marius Gedminas wrote:
> On Fri, Jul 04, 2008 at 07:26:57PM +0300, Panagiotis Papadakos wrote:
>   
>> Lets say that I have a file on my local branch,
>> which is under version control. I need to make
>> some changes to this file so that the code of the branch
>> can work using my personal options (lets say
>> this is a config file). And I don't want to accidentally
>> commit the changes I have made to the central branch.
>> Is there any way I can somehow 'lock' the file?
>>     
>
> I've been missing this sort of thing in Subversion.  It would be nice if
> Bazaar had a way to mark files "uncommittable".
>   

I seem to remember something like this in tla (Gnu Arch): there was a 
kind of files called "precious" which were copied if a new branch was 
created, but weren't taken into account when committing (tla didn't 
recognise them as source files).



More information about the bazaar mailing list