[translations] how to handle snippets commit if you don't have push access |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: LilyPond Translation <translations@xxxxxxxxxxx>
- Subject: [translations] how to handle snippets commit if you don't have push access
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Thu, 05 Jan 2012 16:21:32 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=pKFp1XsbThWGn79Mad2jt2z8aR6jcQTT61sae6DMLSQ=; b=dqXHg9Cn/HAW2q0F73u0bNLek8Vg2UpsKFYFvWPLqPXqCOkhTwpAT2i/ymTrU/xW7Z FPOar3z3XkZ9leXgaorNbPIFGs/ILjWVSsYr4XQEs+ifogbJtNOFF/Dqm8Cu3nkwveS6 4f6p/dru4UE+yyBPSDKWtccRSkDjzopsv+pT4=
Hi,
I've just sent the first chapter of NR to the italian proofreader.
While waiting for his feedback, I have a few questions about the patches
that I'll have to send.
It's all about the snippets management, which caused me some headache a
couple of months ago:
http://lilypond-translations.3384276.n2.nabble.com/CG-5-8-3-updating-committish-of-lsr-snippets-td6852329.html
I'm thinking about sending two patches first and then a third after the
two are applied.
The first two patches will be:
1) files related to notation manual
2) snippets updated by makelsr
I think it's better to split them, right?
The third:
3) my .texidoc files containing the committish generated by Francisco
when committing patch 2.
The reason is: I can't place the committish of my local commit, because,
since I don't push the patch, the real committish will be different
(BTW, as I don't have push access, my local committishes are always bad
objects).
I think also that I'd better update the committish of all the other
it/*.texidoc files in order to stop check-translation to put garbage in
the diff :)
Of course, after checking that nothing has changed in the title or in
the description of the snippets.
Does it make sense?
Thanks,
Federico