Tracking permissions [was: Re: [PATCH] Branch and pull-- now with remote]

[Martin Pool]

On Thu, 2005-06-02 at 16:10 -0700, Dan Nicolaescu wrote:
> Benno <benjl at cse.unsw.edu.au> writes:
> 
>   > On Wed Jun 01, 2005 at 18:36:17 -0400, Aaron Bentley wrote:
>   > >> I believe this is mostly because bzr doesn't actually track file
>   > >> permissions yet, is that true?
>   > >
>   > >That's right.  Actually, Martin was only planning on tracking the
>   > >execute bit.
>   > >
>   > 
>   > I think this is a very good idea. When working on a source base, or more
>   > importantly trying to share it with others on the same machine, being able
>   > to freely change read & write permissions is quite important.
> 
> The reverse is also true. In some cases is important that the
> permissions are preserved. For example when versioning files in ones
> home directory it is desirable that some of the dot files (like
> .emacs) to be readable for everyone, but not the
> addressbook or .ssh. Similarly sometimes it is desirable that some
> files or directories are read-only. 

That's true, and I'd be happy to add a clean patch for it.  However, bzr
is primarily a _source code_ management tool and in that context doing
any more than the X bit is usually just annoying. 

-- 
Martin