-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Use svn blame.
It is unfortunate that Subversion doesn't record merges. As I understand
it, this will no-doubt come about as part of the planned for the future
merge tracking.
On Feb 17, 2005, at 11:33 PM, Diviner wrote:
> Ben Collins-Sussman,
>
> No, I should apologize to you for my bad english. So let me explain
> more
> details in different way.
>
> Let's say Project leader named Tom and also as a SVN login name. And
> some others programmers
> such as John, Peter, David. They are all project team's member.
>
> Our workflow is that, Tom splits a project to several modules and put
> each module into separate
> branch. Then distributes branch to certain programmer, such as Module1
> for John, Module 2 for
> Peter, and so forth. After programm done his module, Tom double checks
> his module code from
> the related branch and do a brief test. If there is ok, Tom merge this
> branch to trunk.
>
> After the days, Tom find that a file has an error. He want to find out
> the programmer who write
> the code to fix it off. But if Tom check the "change log" from trunk,
> all files is changed by Tom
> because all the files in trunk is updated (merge & commit) by Tom
> himself. That is the main problem
> what I am meeting now. It is hard to find out the Real Developer of the
> code in a lot of Branches.
>
> --
> Best regards,
> Diviner.
>
>
>> I apologize... I don't understand what you're trying to do. Maybe you
>> can explain in a different way, or with a detailed example.
>>
>>
>> On Feb 17, 2005, at 7:50 PM, Diviner wrote:
>>
>>> Ben Collins-Sussman,
>>>
>>> It is a lot of branch there, so it is difficult to check each branch
>>> for
>>> a file.
>>>
>>> --
>>> Best regards,
>>> Diviner.
>>>
>>>>
>>>> On Feb 17, 2005, at 2:12 AM, 柱民 wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Our workflow on SVN is that, lets developers work on a branch.
>>>>> After
>>>>> a brief testing or screening by senior developer, then merge the
>>>>> branch
>>>>> to trunk by senior developer.
>>>>>
>>>>> The problem is that it is hard to trace back which developers is
>>>>> involved
>>>>> in particular file before and is involved in which branch.
>>>>>
>>>>> How to check it out?
>>>>>
>>>>
>>>> Run 'svn log' on different branches? That will show you who
>>>> committed
>>>> what, and where, and when.
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>>
>>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCFZ12zaKkuvKwKvcRAq4kAJ44I3/Z6AZzmqqSkEjV3B2Dmlaq9QCbB4m7
53xTKnUwMHwE3zw0ZB8j3sg=
=SEqP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 18 08:49:13 2005