lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Git translation branch policy change: merge with and from stable/2.1


From: Francisco Vila
Subject: Re: Git translation branch policy change: merge with and from stable/2.16
Date: Sat, 8 Sep 2012 01:02:32 +0200

2012/8/19 John Mandereau <address@hidden>:
> Hi Francisco,
> Il giorno sab, 18/08/2012 alle 23.56 +0200, Francisco Vila ha scritto:
>> and allright. I have many pendant tasks as a plain translator; if I
>> need something more than pushing to translation to be done, I'll say.
>
> If your pendant tasks had master branch as upstream, you should be fine
> with completing them and pushing them to translation with this new
> policy, because at some point after you went to vacation, stable/2.16
> was branched out of master, and then translation and stable/2.16 have
> been merged together and are equal as I'm writing this.

Hi John,
as things are today, can we keep doing the usual merges of
translation-->staging and master-->translation?

Translators: I am very busy at home these days. I can perform those
tasks on Sep 10 at soonest.
-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com



reply via email to

[Prev in Thread] Current Thread [Next in Thread]