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

Re: SVN keyword replacement

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 19 Feb 2019 16:19:57 -0500

Mark Phippard wrote on Tue, 19 Feb 2019 20:53 +00:00:
> It ought to cover everything. If this looks like it is going to take a
> considerable amount of your time then you might want to post what you
> plan to do on the dev@ mailing list. There is no point spending time on
> this if someone plans to veto it. As I noted, there are reasons some
> might object to this idea. If it is a fairly quick patch then you might
> as well let the patch show what you have in mind.

You probably want to use one of the svn_*_skip_ancestor() functions in
svn_dirent_uri.h. You can look at 'svn info' for how to compute the wc
root path, if it isn't already available.

That said, I don't see anything preventing us from specifying a boolean
svn:x-branchroot nodeprop in 1.12. We don't have to nail down the API,
or to add subcommands, or anything else; we can just specify it and see
what the ecosystem comes up with... though we _could_, say, introduce
an $X-branchrootrelativeurl$ keyword alongside it.

The X- in the names is to make them "experimental", i.e., covered by limited
compatibility promises. With our recent shift to LTS and non-LTS releases,
we can start using non-LTS releases as vehicles for getting wider feedback
on ideas, by shipping those ideas as "experimental".


Received on 2019-02-19 22:20:08 CET

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