Lucky for everyone, it turns out I am an idiot. I found a non-ignored file
that was lying around.
I will be taking a giant dose of RTFM and going back to production now.
2008/4/9 Mark Phippard <markphip_at_gmail.com>:
> On Wed, Apr 9, 2008 at 8:02 PM, Richard Fairthorne
> <richard.fairthorne_at_gmail.com> wrote:
> > I believe that Subclipse wrongly marks folders for outbound changes when
> > changes are made to deeply nested files marked for svn:ignore. I feel
> > this behavior is a bug. It can be tested thusly:
> > In a controlled project, create a directory or any number of levels of
> > directories.
> > In the deepest directory create a file.
> > Add the file to SVN:ignore
> > Commit the project.
> > Change the file.
> > Make sure that "Compute deep outgoing state for folders" is enabled.
> > In a default install, your top level folder will appear red (indicating
> > outgoing changes). Attempting to commit those changes will result in
> > being committed, as there are no changes to controlled files.
> > Does anyone have comments before I file a bug report?
> The svn:ignore property can only be set on folders. So when you ask
> to ignore a file, what has to happen is the svn:ignore property of the
> parent folder is added/modified to include the pattern you tell it to.
> If this folder, and any of its parents are not currently versioned,
> then they all have to be svn add'ed to SVN so that a property can be
> set on them. It sounds like that is what is happening, although they
> should show up in the commit dialog.
> Try it with the 1.3.x development releases and include screenshots if
> it still seems like a problem.
> Mark Phippard
Received on 2008-04-10 02:59:34 CEST