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

Re: svn: Commit failed (details follow): 'file' is not under version control

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Fri, 9 May 2008 22:19:30 +0200

On Fri, May 9, 2008 at 9:15 PM, Mark E. Hamilton <mhamilt_at_sandia.gov> wrote:
> Erik Huelsmann wrote:
> >
> >
> > > I have a sparse working directory that contains a file which has been
> > > ignored, and some sub-directories, some of which were updated and some
> of
> > > which were checked out (so my working directory is disjoint so I can't
> just
> > > do 'svn commit -m Test'.) I can get the status using a wildcard:
> > >
> >
> >
> > The wildcard expands to a list of files including the unversioned
> > file. If you run svn commit without the wildcard, the above should
> > work.
> >
> In any working directory there are three classes of files; revisioned,
> unrevisioned but ignored, and unrevisioned. The first two are known to svn;
> the third are not. In my example everything that the wildcard expands to is
> known to svn; the file it is complaining about is unrevisioned but known
> (due to the svn:ignore property on the working directory.)
> The 'svn status *' and 'svn update *' both understand these three classes,
> so my question is why doesn't 'svn -m Test commit *'? Why doesn't it ignore
> the ignored files? Is there a situation in which this would be the wrong
> thing to do?

It doesn't ignore the ignored files, because ignored files are
something specific to svn status/ svn add, not to commit. You can
still explicitly add+commit ignored files. This is what svn is
complaining about with your wildcarded command: the file is
unversioned (be it ignored) and you can't commit unversioned files...



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-09 22:19:53 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.