On Wed, Apr 15, 2020 at 2:03 PM Attila Kinali <attila_at_kinali.ch> wrote:
> On Wed, 15 Apr 2020 13:53:07 +0200
> Branko Čibej <brane_at_apache.org> wrote:
> > I don't remember svn:ignore *ever* working the way you describe. Can you
> > tell us which version of Subversion you were using? Are you absolutely
> > sure it wasn't modified to behave as you describe?
> That was like 10-15 years ago. I don't remember which version we
> used back then.
> > Like I said, it did not change. Files that are already
> > version-controlled cannot be ignored. This was part of the original
> > svn:ignore design spec, and the behaviour is actually based on .cvsignore.
> Hmmm.. could it be that we were relying on a bug?
> > > Is there a workaround that we can use?
> > Sure, don't commit the files that you don't want in the repository.
> > Instead, create a template that each user can rename to an (ignored)
> > local name.
> Yes, but mistakes happen. This is a project we are doing together with
> a bunch of computer scientists. These are not computer savy people!
> I'm glad we are using any SCM in the first place and not some Dropbox
> with zip files or something.
> Seem's like I have to think about changing our workflow..
FWIW, the behavior you want is a very old feature request that
unfortunately never got implemented:
https://issues.apache.org/jira/browse/SVN-2858 (Support file property
which indicates that commit must be manually forced)
Some of us know it as the "svn:hold" property.
I think this still could be implemented if someone stepped up to do it
(starting by dusting off the old design docs and discuss approaches on
dev@). But it won't be easy, because there is a lot of interaction
with other existing features.
Received on 2020-04-15 14:43:14 CEST