Eric Gillespie <epg@pretzelnet.org> writes:
> cmpilato@collab.net writes:
>
> > admittedly that your idea may not be a good one, I was just trying to
> > help you remove your uncertainly of its Badness. ;-)
>
> But you didn't remove the uncertainty:
>
> > > Yeah, see the problem here is that you set your format string property
> > > on trunk. But what if I only check out some sub-tree under trunk?
>
> > Like i said, it climbs the directory tree until it finds it (or
> > doesn't).
>
> In any case, defining the custom keyword on all 1000 files that
> are going to have it in my repo is not an option. What happens
> when the keyword changes?
It's the "or doesn't" case that scares me...but then, now that I think
about it, it doesn't really scare me that much. I mean, if it doesn't
find the keyword property, the worst thing that happens is that that
keyword won't get expanded. Even if the user commits that file, it
shouldn't cause any problems because again, the keyword won't be
treated as special.
Alright, I'm convinced. There's some merit to your method.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 3 18:19:02 2002