head	1.5;
access;
symbols
	proto-0_7_3:1.5
	proto-0_7_2:1.5
	proto-0_7_1:1.5
	proto-0_7:1.5
	proto-0_6_8:1.5
	proto-0_6_7:1.5
	proto-0_6_6:1.5
	proto-0_6_5:1.5
	proto-0_6_4:1.5
	proto-pre_events_0_6_4:1.5
	pre-IS-A:1.5
	proto-0_6_3:1.5
	proto-0_6_2:1.5
	proto-0_5_3:1.5
	proto-0_5_2:1.5
	proto-0_5_1:1.5
	proto-0_5:1.5
	proto-0_4_5:1.5
	proto-0_4_4_1:1.5
	proto-0_4_3:1.5
	proto-0_3:1.5;
locks; strict;
comment	@# @;


1.5
date	2001.08.06.23.37.16;	author kasplat;	state Exp;
branches;
next	1.4;

1.4
date	2001.08.06.23.26.21;	author kasplat;	state Exp;
branches;
next	1.3;

1.3
date	2001.08.06.23.23.40;	author kasplat;	state Exp;
branches;
next	1.2;

1.2
date	2001.08.06.23.19.30;	author kasplat;	state Exp;
branches;
next	1.1;

1.1
date	2001.08.06.21.12.10;	author kasplat;	state Exp;
branches;
next	;


desc
@@


1.5
log
@going back to favorites.py. If you want to use searchexplorer and not
have your own personal favorites copied into cvs when you do an update
then either be very careful to not ever commit an update containing
favorites.py or better yet, just copy the searchexplorer directory
to a different directory and use that copy for your own personal use.
I guess if a file is checked into cvs, then the .cvsignore doesn't
actually ignore the changed file on your local system.
@
text
@.cvsignore
*.pyc
*.log
*.pyw
@


1.4
log
@and changing to favorites.data - this is getting old real fast
@
text
@a1 1
*.data
@


1.3
log
@changed favorites.py to favorites.data.py and updated .cvsignore and
searchexplorer.py once again
@
text
@d2 1
a2 1
*.data.py
@


1.2
log
@yet another attempt to keep favorites.py from being updated in cvs
which once again appears to not be working
@
text
@d2 1
a2 1
f*.*
@


1.1
log
@samples modified for package use
@
text
@d2 1
a5 1
favorites.py
@

