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

Re: Requests

From: Gavin Lambert <tsvn_at_mirality.co.nz>
Date: Mon, 23 Sep 2013 12:30:26 +1200

On 9/21/2013 2:59 AM, Quoth Ben Fritz:
> Why is this a pathological case?
> Every project I work on has multiple components which can be worked on
> separately. We have supporting documentation, we have GUI definition
> graphics files, we have the code of course, we have separately
> compiled libraries that go into the project, etc. There are tons of
> reasons why we might check out a subfolder.

Maybe it's a cultural/policy thing then. We tend to use
single-shared-trunk layout so everybody has a copy of the entire trunk
at all times -- there's never any reason to check out a subfolder.

But even in a trunk-per-project setup I would think it'd make the most
sense to still check out the entire project at once. After all, the
people working on the documentation would want to know when a change
occurs in the GUI graphics that would require them to update
screenshots, etc. And if that's not the case, then maybe the definition
of "project" is in the wrong place.

In either case though, only a small subset of folders in any given
repository would actually represent a new top-level "project". Most are
just organisational or required by dev tools. TSVN doesn't have any way
to tell the difference, but presently it seems to be assuming that every
folder is a project, which seems like the wrong call to me.

> And how exactly would it be obvious? The only sign a user would have
> that something is weird, is that the bug ID entry field would be
> missing from the dialog. Those bugtraq properties got set up once at
> project creation, nobody ever looks at or touches them anymore. I'd
> bet a lot of my team members don't even know they're there or what
> they do if they DO notice them.

I was meaning that it would be obvious to the person creating the new
project folder. If only because they're supposed to put something in
the bugtraq info before committing. (Which again is a cultural thing I

In any case, creating copies of the properties makes them impossible to
maintain / update, because there is no longer a single definitive
source. At least with the official new 1.8 recursive lookup the
original issue can be mitigated without copying -- now we just need to
be able to convince TSVN to stop copying.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-09-23 02:31:18 CEST

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

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