[vtk-developers] RE: Tag policy
Volpe, Christopher R (Research)
volpecr at crd.ge.com
Tue Dec 10 08:56:24 EST 2002
Thanks, Ken. I may make one, maybe two, tags in the short term (next couple of months) while I
find/implement an alternative solution. I spent a great deal of time yesterday searching the web for
a tool to create the equivalent of tags without touching the repository, but without any luck.
Therefore, I'll implement a script of some sort to do this. I imagine that other users, particularly
those using anonymous repository access, would find such a solution useful, so I'll make it available
when I have something working.
thanks,
Chris
> -----Original Message-----
> From: Ken Martin [mailto:ken.martin at kitware.com]
> Sent: Tuesday, December 10, 2002 8:48 AM
> To: Volpe, Christopher R (Research); 'Vtkdevelop (E-mail)'
> Subject: RE: Tag policy
>
> Hello Chris,
>
> There is no formal policy, but I would suggest the following.
> If you are looking to add a couple tags a year then go ahead.
> If you are looking to add a bunch of tags a year (or heaven
> forbid a tag a week) then it would be better to look for
> another mechanism.
>
> Thanks
> Ken
>
> -----Original Message-----
> From: vtk-developers-admin at public.kitware.com
> [mailto:vtk-developers-admin at public.kitware.com] On Behalf Of
> Volpe, Christopher R (Research)
> Sent: Monday, December 09, 2002 12:01 PM
> To: Vtkdevelop (E-mail)
> Subject: Tag policy
>
> Question:
> What is the policy (if any) on "J. Random User" tagging the
> repository? I realize that adding a tag doesn't necessarily
> affect other users, but then if a thousand users started
> adding their own tags, it might clutter things up a bit. If
> adding a tag is something that is frowned upon, or requires
> explicit approval, is there some form of alternative? It
> would be really neat if there were some way to take a
> snapshot of what file revisions I happen to be working with,
> and store that information locally so that I can use it with
> some kind of checkout procedure that will pull out all the
> appropriate revisions, but have that info kept client-side so
> as not to clutter up the repository. Any thoughts or suggestions?
>
>
More information about the vtk-developers
mailing list