subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Becroft <djcbecr...@gmail.com>
Subject Re: 1.7.x - merge now accesses all files in WC?
Date Thu, 02 Dec 2010 21:43:46 GMT
On Wed, Dec 1, 2010 at 7:34 PM, Philip Martin <philip.martin@wandisco.com>wrote:

> Daniel Becroft <djcbecroft@gmail.com> writes:
>
> > Under 1.7.x, the following file(s) are accessed (merging the same
> revision
> > as above):
> >
> >  - .svn\wc.db
> >  - Every versioned file in the working copy
>
> What does "accessed" mean?  stat(), open(), read(), write()?
>

I'm not sure. I'm pretty sure it's not read() or write(), but it's most
likely stat().


> There is a known issue that involves a stat() on files when accessing
> the metadata (svn_wc__db_pdh_parse_local_abspath).  Is that what you are
> seeing?
>

I've just managed to build/install trunk on my ubuntu box at home (first
application I've ever compiled on it - yey!).

What debugging tools would you recommend to investigate this further? I've
seen output posted that lists function names, and time spent on each.


> > I can't see any reason why all these files would need to be accessed. I
> seem
> > to recall some discussion about preventing/warning merging into modified
> > working copies, could this be the cause?
>
> The new check is for a single revision working copy, not an unmodified
> one.
>

Ah, that makes more sense, I guess. Checking for an unmodified WC would mean
that the ability to run consecutive 'svn merge -c' commands would be
removed.

Cheers,
Daniel B.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message