gnu-arch-users
[Top][All Lists]
Advanced

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

Re: [Gnu-arch-users] Fwd: not changing default =tagging-method


From: John A Meinel
Subject: Re: [Gnu-arch-users] Fwd: not changing default =tagging-method
Date: Tue, 05 Jul 2005 18:44:51 -0500
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Brian May wrote:.
...

I notice with a recent baz archive it is:

backup 
^.*(~|\.~[0-9]+~|\.bak|\.sw(o|p)|\.orig|\.rej|\.original|\.modified|\.reject|\.(o|a|so|core|so(\.[[:digit:]]+)*))$|^core$
unrecognized ^$

What is the difference between a .swo and a .swp file?


Both are vim backup/temporary files. But if .swp exists, usually vim
creates a new one with .swo. And if that exists it uses .swn, I'm not
sure how far that goes, because I've only seen .swn.This happens if you
open the same file twice, or if you open the file, and your machine
dies/network connection dies.

I guess my above quotes above serve to demonstrate different people
have different opinions of the usefulness of the "unrecognized"
category.


Unrecognized means give an error (generally). Backup means ignore it
entirely.
It was Tom's original belief that trees should be clean before you
commit. (And that you should generally build outside the source tree
anyway.)

The bazaar people decided that blocking a commit just because there was
a .o file in the tree was poor form, and did away with it. (Same thing
for dot files, and a few other types, tla mainline by default complains
if you have a dot file in your path).

John
=:->

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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