C. Michael Pilato wrote:
> Issue Number:
> Reviewed By:
> * * * *
> Changes:
> [paths]
>
>Might get transformed to:
>
> Issue Number:
> Reviewed By:
> * * * *
> Changes:
> A /trunk/foo
> A /trunk/foo/bar.txt
> ...
>
>Or something like that.
>
>
Not a bad idea.
[snip]
>>>Just for the record. IMHO we don't need it for log templates, either. It
>>>may be sexy to have them generated based on the set of paths to be
>>>committed, but that /is/ overkill IMNSHO.
>>>
>>>
>>I don't think it's at all overkill for situations like the ASF
>>repository. If a single repository-wide log template were good enough
>>for the vast majority of cases, I don't think we'd have seen the
>>per-directory functionality in CVS.
>>
>>
>
>I think there's no doubt that we want per-directory-tree log message
>templates. But then, I also want per-directory-tree generic
>server->client configuration dictations, for things like auto-props
>and ignores and such.
>
>
Just to avoid misunderstandings: I totally agree that, if we need log
templates at all, they have to be per-directory.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 17 23:45:38 2005