lilypond-devel
[Top][All Lists]
Advanced

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

Re: showFirstLength


From: Reinhold Kainhofer
Subject: Re: showFirstLength
Date: Mon, 20 Oct 2008 21:09:49 +0200
User-agent: KMail/1.9.10

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Montag, 20. Oktober 2008 schrieb address@hidden:
> I don't know what to do next; should I open a new issue with the updated
> code? Or is it possible to upload a new patch within the same issue?

Yes, simply do 
git-cl upload
to upload a second (updated) patchset to the same issues already stored in 
your local branch (check that "git-cl issue" has an issue set for your 
current branch....). 

I suppose you are working in a temporary branch anyway, are you? If not, you 
better do a "git checkout -b newbranchname origin/master" to create a branch 
and switch to it. You probably also need to adjust the issue<=>branch map 
in .git/cl-mapping to associate your new branch to the already existing issue 
(you don't usually do this manually, but you create the local branch before 
you upload an issue...).

Cheers,
Reinhold


- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI/Nd9TqjEwhXvPN0RAv74AKCj7ING2iJ0nntfNLo8ore8fV4iKQCgkaQw
0wmOukqAfvCbKgrs1h/6TnU=
=a22C
-----END PGP SIGNATURE-----




reply via email to

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