[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] [BUG] (optional permissions foo)

From: Tom Lord
Subject: [Gnu-arch-users] [BUG] (optional permissions foo)
Date: Thu, 23 Sep 2004 22:09:36 -0700 (PDT)

Good idea, at least at first and second glance.

------- Start of forwarded message -------
X-42-Pre-Check: Attempted
To: Dustin Sallings <address@hidden>
From: Miles Bader <address@hidden>
System-Type: i686-pc-linux-gnu
Blat: Foop
Date: Fri, 24 Sep 2004 13:01:11 +0900
In-Reply-To: <address@hidden> (Dustin
        Sallings's message of "Thu, 23 Sep 2004 20:47:11 -0700")
Content-Type: text/plain; charset=us-ascii
Cc: Arch Users <address@hidden>
Subject: [Gnu-arch-users] Re: bitkeeper vs tla
X-BeenThere: address@hidden
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Miles Bader <address@hidden>
List-Id: a discussion list for all things arch-ish <>
List-Unsubscribe: <>,
List-Archive: <>
List-Post: <mailto:address@hidden>
List-Help: <mailto:address@hidden>
List-Subscribe: <>,
Sender: address@hidden
X-Spam-Checker-Version: SpamAssassin 2.64-42mail (2004-01-11) on
X-Spam-DCC: SdV: mail 1179; Body=2 Fuz1=1 Fuz2=2
X-Spam-Status: No, hits=-4.8 required=4.5 tests=AWL,BAYES_00 autolearn=ham 
X-42email-MailScanner-Information: Please contact for more information.
X-42email-MailScanner: Found to be clean
X-UIDL: e1bf716cbf786d213058573878003384

Dustin Sallings <address@hidden> writes:
>> Well, if you can do hard-linked source trees, I've found that my 'tla 
>> changes' time goes *way* down.
>       Hmm...  I didn't try that one, but it scares me just a bit.  I have a 
> fear that some tool I use might end up screwing up the revlib.

A well-founded fear: I used --link for a while, with good effect (my main
tools, emacs and patch, both deal well with hard-links), but had to trash
my entire revlib after a single ill-considered shell-redirection.
Downloading everything again over a slow net link was not fun.

I think --link is not a good idea in general except for trees that you
won't modify (though temporary trees that you don't modify are in fact a
very useful and common thing), or are similarly only used in restricted

Perhaps tla could somehow assist this by providing a way to easily make
all files in a project tree read-only, e.g., `tla get --link --read-only'?
I guess it would have to add some meta-data indicator to tell mkpatch not
to do any permission bit comparisons against that tree.

- -Miles
- -- 
Suburbia: where they tear out the trees and then name streets after them.

Gnu-arch-users mailing list

GNU arch home page:
------- End of forwarded message -------

reply via email to

[Prev in Thread] Current Thread [Next in Thread]