[vbox-dev] Latest manual

[MENGUAL Jean-Philippe]

Hi,

Well... if 4.3 doesn't have any public repo and as I haven't any input 
method in Oracle workspace,  I will go on translating the trunk only. If 
you consider that one change could be applied in 4.3 branch, as you are 
the only people able to know what happens in this branch, you're free to 
apply my patch to 4.3 too. If needed, you can request my help

Regards,

Le 23/10/2013 17:27, Michael Thayer a écrit :
> Hello,
>
> On 23/10/13 17:24, Klaus Espenlaub wrote:
>> On 21.10.2013 23:55, MENGUAL Jean-Philippe wrote:
>>> Le 21/10/2013 09:12, Michael Thayer a écrit :
>>>> On 18/10/13 22:56, MENGUAL Jean-Philippe wrote:
>>>>> ok so what's the preferred solution now? How can I trigger the 4.3
>>>>> branch to update synchronously and, if possible, know when things
>>>>> change?
>>>> If you are interested in maintaining both manuals - the 4.3 one and
>>>> the development tree one - in parallel, one way would be for me to
>>>> send an e-mail to this list before minor version releases saying which
>>>> change sets from the trunk manual were back-ported to 4.3.  Then you
>>>> could copy over the relevant sections of text from the trunk manual.
>>>> Does that seem reasonable?  As I said, I think that considering the
>>>> 4.3 manual translation as finished and just continuing work on trunk
>>>> would also make sense if maintaining two versions is a pain.
>>>>
>>>
>>> I propose 2 alternatives:
>>> 1. Give me the URK to checkout the 4.3 branch and, when there's a
>>> change, simply notify me by mail (or notify here). I'll work then with
>>> svn diff to patch.
>>> 2. I go on trunk, and you apply changes there in 4.3 release. But I'm
>>> not sure it's possible given the dev process of vbox.
>>>
>>> Hence: I propose the 1st alternative.
>> Unfortunately there is no publicly accessible repository which contains
>> any VirtualBox branches. It's a long-standing todo (and we want to get
>> that done, to avoid any misunderstanding) which we couldn't complete
>> because it needs quite some effort to make the involved tools smarter.
>>
>> Trunk and 4.3 will diverge relatively quickly, so 2. won't work in the
>> long run.
> As I mentioned though, there tend to be very few changes to the manual
> after a release, so keeping up with trunk and manually copying the few
> relevant text sections from trunk to the 4.3 manual might be an option.
>
> Regards,
>
> Michael


-- 

Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: texou at accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu