|
From: | Federico Bruni |
Subject: | Re: CG 3.2.1: missing instructions on how to track the translation branch |
Date: | Tue, 07 Aug 2012 23:24:34 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 |
Il 07/08/2012 22:43, Colin Hall ha scritto:
On Tue, Aug 07, 2012 at 07:08:20PM +0200, Federico Bruni wrote:Il 07/08/2012 18:53, Graham Percival ha scritto:If you want to create a new branch to retain commits you create, you maydo so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_namemaybe try following this advice? git checkout -b origin/translationoops I prefer this: git checkout -b translation origin/translation so the local branch will be named translation instead of origin/translationFederico, is there a bug here to be captured?
There's any open issue for the CG? I can't find it.. This paragraph is marked as obsolete: http://lilypond.org/doc/v2.15/Documentation/contributor/downloading-remote-branches So if you want to open an issue, here's a quick and dirty description:We currently recommend in 3.2.1 to use 'git clone' to download the repository. This command downloads all the remote branches and makes the checkout of the master branch.
3.2.4, Downloading individual branch, is obsolete and should be removed.What we should keep are the instructions on how to start working on a new branch, different from master, that is:
git checkout -b branch origin/branch This means that translators should use: git checkout translation origin/translation -- Federico
[Prev in Thread] | Current Thread | [Next in Thread] |