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

Re: GIT/Perforce like .svnignore

From: Branko Čibej <brane_at_apache.org>
Date: Mon, 2 Dec 2019 12:08:31 +0100

On 02.12.2019 11:48, Paul Hammant wrote:
> > ... "pointing at GitHub not going to solve anything" ...
>
> I was pointing at a GitHub repo in order for the OP to use that, and
> perhaps contribute to it there. It can easily be perfected there in
> (say) Python, and in a couple of years time re-implemened in C in for
> Svn on Apache's canonical Svn 'upstream'.
>
> I get that the implementation cost is (say) 4x higher in C with tests,
> and think prototyping things in higher level languages is a great idea.
>
> So I'd say it is solving the OPs problem imperfectly.

I think the main problem with (one of) those examples is that they
populate the svn:ignore property from the contents of some file. When
you change the file ... what happens? Do existing patterns that don't
match the new template get deleted? What if they were added to the
svn:ignore property manually?

And so on. So, sure, prototyping is a good idea, but when it comes to
considering the semantics you want to have in Subversion, some extra
thought is required.

-- Brane
Received on 2019-12-02 12:08:34 CET

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.