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

Re: problem arising from early entry deletion

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-03-20 03:39:54 CET

Ben Collins <bcollins@debian.org> writes:

> On Sun, Mar 17, 2002 at 09:03:10PM -0600, Karl Fogel wrote:
> > Ben Collins <bcollins@debian.org> writes:
> > > Thought about that several minutes after I sent the email. Seems you
> > > can't really avoid having the old way in place. I know it has caused me
> > > a lot of problems with my project. Me being the only one committing to a
> > > repo, I still had to "svn up" after each commit to prevent conflicts
> > > from popping up (presumably because of this issue).
> >
> > Just curious, what have you been doing? What symptoms do you see?
> >
>
> Import 2.0.0 kernel, apply patches (2.0.1, 2.0.2, 2.0.3, etc.) and
> commit each one. In between I have to svn up, or I'll send up with some
> sort of out-of-date error from a previously deleted entry.

Could this the same problem as issue 657?
http://subversion.tigris.org/issues/show_bug.cgi?id=657

-- 
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 20 03:40:42 2002

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