Re: svn commit: r10592 - branches/1.1.x/subversion/po

>>>I might be missing something, but don't we normally commit changes to the
>>>trunk and then merge them to the branch? Is there any exception to this
>>>rule?
>>>
>>>
>>Almost no exceptions, right.
>>
>>Now, this might have been a merge where niqueco just forgot to say the
>>source revision of the merge... ?
>>
>>
>Yes. Didn't think of that. Do you fix the message if that's the case,
>Nicholás?
>
>

Er.... sorry. I've just created my own .po handling policy for merges. I
wasn't following the discussion in the list very closely. What I had
thought on doing is just to concentrate on the branch, and when
subversion is released, forward port the changes to the trunk. I think
this much more simpler, and the result is the same. What do you think?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 12 01:13:13 2004