Greg Hudson <ghudson@MIT.EDU> wrote on 05/19/2005 12:01:53 PM:
> On Thu, 2005-05-19 at 11:45 +0200, Erik Huelsmann wrote:
> > Also, we seem to (mostly) forget that a network turnaround may not
> > always be a http or svn connection: setting up svn+ssh connections -
> > if not reused - may be a major annoyance to users when they don't have
> > ssh-agent set up.
> In the simple case of "svn commit" with no provided log message, I
> assume Karl envisioned using the same RA session to fetch the template
> and to perform the commit.
> In the case of "svn commit --template-only" followed by "svn commit -F
> file", there would obviously be two RA sessions.
> > If these are the underlying assumptions, then why won't the
> > per-directory static template work?
> I commit twenty files in ten widely separated directories. Which
> directory's template gets used?
> This is one of the questions Karl initially started out trying to
> answer, and he found that the answer wasn't obvious, which led him to
> the idea of punting to a server hook. Yet you and four other of this
> morning's contributors to the conversation seem to have simply glossed
> over the question, instead considering issues like how the user might
> easily set the same template for many directories. Perhaps you all have
> some simple, adequate idea in mind ("the template for the anchor of the
> commit", perhaps), but I really can't tell.
Yes, you are right, we did gloss over this. In Subclipse we would use the
anchor of the commit, although since we do not have inherited properties,
we will start with the anchor of the commit and then move up the WC
hierarchy if necessary to find the property. Using Subversion as an
example, if the property were only set on the trunk folder and that is
what you checked out in your WC, you can do a commit at a lower level,
such as the libsvn_fsfs folder and we will walk up the WC to find the
property if necessary.
If we had inherited properties, we would just use the anchor of the
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 19 18:26:09 2005