[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: Log Message Templates via new hook.

From: <kfogel_at_collab.net>
Date: 2005-05-20 17:16:46 CEST

"C. Michael Pilato" <cmpilato@collab.net> writes:
> > A: Whose side are you on, anyway? Let's be real. Have you ever
> > seen a template like that? I haven't. They've all been pretty
> > simple things, a few fields to fill in, maybe some reminders,
> > that sort of thing. Sure, they've been *different* from project
> > to project, but I can't say that a template has ever caused a
> > drastic change in the content (as opposed to the formatting) of
> > my log message.
> Q: I guess you're right. Which makes me wonder why those
> Subversion guys designed such a complex
> network-turnin'-around, hook-script-generatin' system for such
> a simple, basically static result?
> Sorry. Couldn't resist. :-)

No, I'm glad you didn't -- I was hoping someone would say this, so I
could rebut it :-).

The simplicity and staticness of any individual template do not imply
simplicity in the *process used to produce* that template. The
production process may be arbitrarily complex. It may involve, for
example, questions of which directory's template "wins" if there is a
per-directory, or per-project-root, template system going on.

To be even more concrete:

Imagine a system whereby, if one makes a single commit across multiple
projects within a big ASF-style repository, a special log message
template is used that is specifically for multi-project commits. It
would start out with a generalized header that is *only* used when
multiple projects are being committed to at once, and then it would
include the per-project templates of each of those projects, but
perhaps modified in some special way because they're part of this
unusual kind of commit.

Notice that the resulting template is still a simple, static document.
It does not *include* any of the paths being committed. Yet those
paths were crucial in determining the content of the template.

Thus, a complex process can lead to a deceptively simple-looking
result. It is that process we are proposing to support here.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 17:53:46 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.