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

branch(es) for meta-data-versioning

From: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2005-03-01 14:24:44 CET

Hello everybody,

as I wrote the original patches for text-time journaling (and am about to for
other meta-data, like owner, group, mode etc.) I get mails about this
Some of these are off-list, and I count about a dozen people interested.

As I managed to get https-access allowed to the subversion repository I
believe it might make sense to create a new directory (in branches?), where
I'd like to deposit two development branches (branched off /trunk) and a
patch directory.

The first branch would consist of the modification for text-time versioning
(as this is longer used and therefore better tested), and the second for the
(highly experimental) owner, group, mode versioning.

As there are changes to the patches needed I currently should contact each of
the interested people and inform them of the changes.
That doesn't scale.

Therefore I ask for this directory, where I could store my modifications, and
which could be queried by everyone interested.
Other developers wishing to look at the changes could do so, too.

I know that I could do similar things by attaching patches to the existing
issues; but as we've got a central repository I believe we should use it so.

That said, I'd understand if the policy (or feeling) is that
"outsiders" (which means people whose identity [and carefullness regarding
passwords etc.] cannot easily be investigated) or people with insufficent
experience don't get write access to the repository.
I won't take it personally, I'll just have to attach patches again as

Dear core developers, please build an opinion and let me (and other interested
in this features) know.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 1 14:26:25 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.