Re: Feature request <g>

[Alain Fagot <alain@netlinq.nl>]

Tim Endres wrote:
> It appears that what I should do is add a little icon to the table to
> indicate which files have sticky tags, and maybe those that are set
> as "binary" files to help visually.

	Well, I am not sure I got all of the issue here but it seems to me that
what I just did may be of some help to some people.  In my company we
are using sticky tags to mark branches (one for each developer, one to
merge the current developments and one to store the delivered
versions).  In WinCVS the sticky tag appears between the revision number
(found to be not human readable according to some ;-) and the
timestamp.  That is just what I reproduced.

	If there is some interest (i.e. I understood correctly your debate), I
can post my patch.

> The second is a tag placed in the entry line for a file in
> CVS/Entries. This tag applies only to the file in question, and I
> believe exists only when a specific file is updated with a tag

	Here, I am not sure whether I did something wrong but giving a command
argument of "-r branch-name" to the update command resulted in a
confused display with a new folder having an empty name and other
confusion.  I could see in the Output window that the file names got a
double slash.  This is my next assignment (did I tell we are relying on
sticky tags? ;-).

Alain.