On 22 Jun 2005 17:34:04 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> > I don't see why the revprops would need to be stored in .svn/ at any
> point...
>
> Well, Subversion already has the 'svn propset --revprop'
> functionality. This would just be another pathway to that same
> ability.
Subversion only talks to the server during particular instances such
as an "svn update" or "svn commit". In between, the changes that the
client needs to let the server know about have to be stored somewhere,
and that's in .svn. To clarify, I'm talking about storing revision
properties via a "svn propset --revprop --nextcommit PROPERTY VALUE"
type of command. You would set the various revision properties you'd
want to do on the next revision, and then run the commit. That way,
you could do an endless variety of revision properties without
worrying about piling them on on top of the command line.
The strange thing about the "svn propset --revprop" is that it sends
its information directly to the server while the regular "svn propset"
stores its information in the .svn directory One uses mainly libsvn_wc
to do its work while the other uses libsvn_ra. Although the syntax is
the same, the two propset commands really act in two completely
different ways.
Maybe that's why everyone is talking about setting revision properties
with the "svn commit" and would probably be the quickest way to
implement it. After all, revision properties are set right now during
the commit process (svn:log, svn:author, etc)
All we really need is a good UI...
How about something like this?
svn commit --revprop <KEY>=<VALUE>,<KEY>=<VALUE>,<KEY>=<VALUE>
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 23 04:54:24 2005