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

Re: How to search between branches (complete)

From: ANGonline <trimante_at_yahoo.it>
Date: 2007-04-17 18:01:05 CEST

>> Méresse Christophe wrote:
>> Imagine a software that has 100 source files and a repository
>> that has one directory for the main trunk and an indefinite
>> number of directory for all the branches, one for each
>> ongoing development thread.
>
> [snip]
>
>> I wonder if there is a way to know, for a certain file, how
>> many branches have done commits on it (well, to be exact,
>> commits on its brothers that have been forked while branching).
>
> I like when people are lighting this problem because that's the one I'm always complaining about :)
> No, there aren't any efficient solution and this big issue (from my point of view) does not seem to concern many users...
>
> <mode_troll_on reason='tentative to have a real debate on this question and why not some ideas to solve it... :)'>
>
Changing this would certainly have a huge impact on the subversion
core, that's probably the reason why the question always generates a
big silence :P
> <mode_troll_off>

> Les Mikesell wrote
> The point of branching is to isolate changes. Why do it if you want to
> treat the copies as though they weren't isolated from each other?

Maybe
I have a wrong mind disposition or I misunderstood the philosophy of
SVN, but what I see is a cooperation problem. Let me try to explain.

Sometimes
arises the need to start an amendment involving a certain number of
files that are already under amendment by other developers.
This
usually can be faced at the end, when each branch is merged back, but
once in a while it happens that the merge is impossibile without
re-engeneering one or all the amendments (well, it can also happen to
start develop something that is already under development elsewere).
This is really really bad and tends to cost too much to be allowed to happen even once in my environment.

I
think that could be always avoided if each developer, BEFORE starting
to develop, can go and see what's going on inside the other branches to
the files he's going to amend, and syncronize himself with the other
developers involved.

Do you see the problem here?
Thanks,
Angelo.

      ___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
http://it.docs.yahoo.com/nowyoucan.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 17 18:01:27 2007

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