|
|
DescriptionAdd alias in Spanish for espanol note names language
Patch Set 1 #Patch Set 2 : New implementation allowing more aliases. #
Total comments: 2
MessagesTotal messages: 10
Ah, so \language "español" will do the same as \language "espanol"? That's nice.
Sign in to reply to this message.
Yes, it adds a copy without deactivating the original. El 02/11/2012 09:34, <janek.lilypond@gmail.com> escribió: > Ah, so \language "español" will do the same as \language "espanol"? > That's nice. > > > http://codereview.appspot.com/**6811060/<http://codereview.appspot.com/6811060/> >
Sign in to reply to this message.
http://codereview.appspot.com/6811060/diff/4001/scm/define-note-names.scm File scm/define-note-names.scm (right): http://codereview.appspot.com/6811060/diff/4001/scm/define-note-names.scm#new... scm/define-note-names.scm:961: ;; add two native utf-8 alisases. Pairs obey cp-like order: '(old new) It should be 'aliases', of course.
Sign in to reply to this message.
https://codereview.appspot.com/6811060/diff/4001/scm/define-note-names.scm File scm/define-note-names.scm (right): https://codereview.appspot.com/6811060/diff/4001/scm/define-note-names.scm#ne... scm/define-note-names.scm:964: (append language-pitch-names I will use two-spaces indenting here. Emacs indent-region inserted the tabs.
Sign in to reply to this message.
Hello. Am I countdowned or rather needsworked? Thanks.
Sign in to reply to this message.
On Mon, Nov 12, 2012 at 9:40 AM, <paconet.org@gmail.com> wrote: > Hello. Am I countdowned or rather needsworked? Thanks. It seems that you're countdowned. I don't know why there are two tracker issues for this (2941 and 2940), but 2940 has status "push". Janek
Sign in to reply to this message.
2012/11/12 Janek Warchoł <janek.lilypond@gmail.com>: > On Mon, Nov 12, 2012 at 9:40 AM, <paconet.org@gmail.com> wrote: >> Hello. Am I countdowned or rather needsworked? Thanks. > > It seems that you're countdowned. I don't know why there are two > tracker issues for this (2941 and 2940), but 2940 has status "push". I only created one. Did not receive the push notice as usual. Thanks for the looksgoodtomeing. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com
Sign in to reply to this message.
On Mon, Nov 12, 2012 at 8:07 PM, Francisco Vila <paconet.org@gmail.com> wrote: > 2012/11/12 Janek Warchoł <janek.lilypond@gmail.com>: >> On Mon, Nov 12, 2012 at 9:40 AM, <paconet.org@gmail.com> wrote: >>> Hello. Am I countdowned or rather needsworked? Thanks. >> >> It seems that you're countdowned. I don't know why there are two >> tracker issues for this (2941 and 2940), but 2940 has status "push". > > I only created one. Did not receive the push notice as usual. Thanks > for the looksgoodtomeing. Well, both of them say "Reported by project member paconet.org". I think git-cl tricked you. Probably the second issue was created when you uploaded second patch set; i suppose you didn't specify the tracker issue number and a new one was created instead of updating existing one. cheers, Janek
Sign in to reply to this message.
2012/11/12 Janek Warchoł <janek.lilypond@gmail.com>: > On Mon, Nov 12, 2012 at 8:07 PM, Francisco Vila <paconet.org@gmail.com> wrote: >> 2012/11/12 Janek Warchoł <janek.lilypond@gmail.com>: >>> On Mon, Nov 12, 2012 at 9:40 AM, <paconet.org@gmail.com> wrote: >>>> Hello. Am I countdowned or rather needsworked? Thanks. >>> >>> It seems that you're countdowned. I don't know why there are two >>> tracker issues for this (2941 and 2940), but 2940 has status "push". >> >> I only created one. Did not receive the push notice as usual. Thanks >> for the looksgoodtomeing. > > Well, both of them say "Reported by project member paconet.org". > I think git-cl tricked you. Probably the second issue was created > when you uploaded second patch set; i suppose you didn't specify the > tracker issue number and a new one was created instead of updating > existing one. I remember git-cl created the rietveld code-reviewing issue and I created the googlecode tracking issue by hand. Is the google code tracking issue created automatically as well? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com
Sign in to reply to this message.
On Mon, Nov 12, 2012 at 8:29 PM, Francisco Vila <paconet.org@gmail.com> wrote: > 2012/11/12 Janek Warchoł <janek.lilypond@gmail.com>: >> Well, both of them say "Reported by project member paconet.org". >> I think git-cl tricked you. Probably the second issue was created >> when you uploaded second patch set; i suppose you didn't specify the >> tracker issue number and a new one was created instead of updating >> existing one. > > I remember git-cl created the rietveld code-reviewing issue and I > created the googlecode tracking issue by hand. Is the google code > tracking issue created automatically as well? yes, unless you're using a very outdated git-cl. jaenk
Sign in to reply to this message.
|
