Commit access

In issue 4776 James wrote: > @Paul, you may want to apply for commit access yourself if you like as I > think you've done enough work for the 'cause' to So I’d like to request commit access. Among other things this will save James the extra work of committing p

Commit access

I'm following the official procedure to ask for commit access and join the developer team. I am a contributor to the translations. I have contributed all the patches for the Catalan translation, which is quite complete. I've been contributing for more than 10 years with the hel

commit access

dear team and Project Manager, I'd like to get commit access. sincerely, Pál Benkő ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Commit access

Paul Morris wrote Monday, February 29, 2016 1:57 AM > In issue 4776 James wrote: > >> @Paul, you may want to apply for commit access yourself if you like as I >> think you've done enough work for the 'cause' to > > So I’d like to request commit acc

Re: Commit access

"Trevor Daniels" writes: > Paul Morris wrote Monday, February 29, 2016 1:57 AM > > >> In issue 4776 James wrote: >> >>> @Paul, you may want to apply for commit access yourself if you like >>> as I think you've done enough work for the

Re: Commit access

Le 29/01/2022 à 17:18, Walter Garcia-Fontes a écrit : I'm following the official procedure to ask for commit access and join the developer team. I am a contributor to the translations. I have contributed all the patches for the Catalan translation, which is quite complete. I&#x

Re: Commit access

* Jean Abou Samra, j...@abou-samra.fr [29/01/22 21:58]: > Le 29/01/2022 à 17:18, Walter Garcia-Fontes a écrit : > > > I support this. I'd just request that you ask in case of > doubt on the technicalities of Git (if you are unsure of > the commit structure, etc. before pushing a patch). > > Than

Re: Commit access

Am Samstag, dem 29.01.2022 um 17:18 +0100 schrieb Walter Garcia-Fontes: > I'm following the official procedure to ask for commit access and > join the developer team. > > I am a contributor to the translations. I have contributed all the > patches for the Catalan transla

Re: Commit access

* Jonas Hahnfeld, hah...@hahnjo.de [09/02/22 21:28]: > Am Samstag, dem 29.01.2022 um 17:18 +0100 schrieb Walter Garcia-Fontes: > > I'm following the official procedure to ask for commit access and > > join the developer team. > > > > I am a contributor to the tran

Re: commit access

Benkő Pál writes: > dear team and Project Manager, > > I'd like to get commit access. I have checked in several of Pál's commits in the past. Just recently another commit that had passed review. For better or worse, I have not personally proofread the commit before check

Re: commit access

On Fri, May 11, 2012 at 11:28:47PM +0200, Benkő Pál wrote: > dear team and Project Manager, > > I'd like to get commit access. Make an account at savannah, and send a request via the savannah project page. I'll act on it within 48 hours (wifi connection at this hotel

request for commit access

Hi all, I'd like to request commit access to push my current and future patches after review. I've just submitted a request on GNU Savannah with username hahnjo. Thanks, Jonas signature.asc Description: This is a digitally signed me

Propose Commit access for Étienne Beaulé

Hello, Étienne has pushed couple of patches now and I wondered if we could perhaps give him full commit access to git? http://git.savannah.gnu.org/gitweb/?p=lilypond.git&a=search&h=4785a3ed7ce03c950f4f1f90ef6f412d038cedc7&st=author&s=%C3%89tienne

Re: Propose Commit access for Étienne Beaulé

James writes: > Hello, > > Étienne has pushed couple of patches now and I wondered if we could > perhaps give him full commit access to git? > > http://git.savannah.gnu.org/gitweb/?p=lilypond.git&a=search&h=4785a3ed7ce03c950f4f1f90ef6f412d038cedc7&st=author&

Re: Propose Commit access for Étienne Beaulé

I have just made a request for inclusion on Savannah with the 'ebeaule' username. Thank you! 2017-09-07 13:07 GMT-03:00 David Kastrup : > James writes: > > > Hello, > > > > Étienne has pushed couple of patches now and I wondered if we could > > pe

Re: Propose Commit access for Étienne Beaulé

James wrote Thursday, September 07, 2017 4:19 PM > Étienne has pushed couple of patches now and I wondered if we could > perhaps give him full commit access to git? Who now has the authority to do this? I don't, and I've lost track of who does now that Han-Wen, Jan and Graham

Re: Propose Commit access for Étienne Beaulé

t know, just assuming here though. Étienne 2017-09-07 17:03 GMT-03:00 Trevor Daniels : > > James wrote Thursday, September 07, 2017 4:19 PM > > > Étienne has pushed couple of patches now and I wondered if we could > > perhaps give him full commit access to git? > > Who

Re: Propose Commit access for Étienne Beaulé

Étienne Beaulé writes: > The Contributor guide just says "Project Manager" without any other > instance of the phrase. David should be able to, as he is a Project > Administrator, the same as the other three on the Savannah member list >

Proposing commit access for Lukas-Fabian Moser

Hi all, Rebasing and merging Lukas' \after patch this morning, I had a wonder moment — wait, he still doesn't have commit access? Seeing his recent patches, which all required substantial discussion and refinement as well as documentation and regression tests (bracketed bass figure a

Re: Proposing commit access for Lukas-Fabian Moser

Absolutely seconded. Am 06.10.2021 um 21:21 schrieb Jean Abou Samra: Hi all, Rebasing and merging Lukas' \after patch this morning, I had a wonder moment — wait, he still doesn't have commit access? Seeing his recent patches, which all required substantial discussion and refinement

Re: Proposing commit access for Lukas-Fabian Moser

Jean Abou Samra writes: > Hi all, > > Rebasing and merging Lukas' \after patch this > morning, I had a wonder moment — wait, he still > doesn't have commit access? Seeing his recent patches, > which all required substantial discussion and > refinement as well

Re: Proposing commit access for Lukas-Fabian Moser

I trust Jean's recommendation on this. Carl

Re: Proposing commit access for Lukas-Fabian Moser

Am 06.10.21 um 21:21 schrieb Jean Abou Samra: Hi all, Rebasing and merging Lukas' \after patch this morning, I had a wonder moment — wait, he still doesn't have commit access? Seeing his recent patches, which all required substantial discussion and refinement as well as documen

Re: Proposing commit access for Lukas-Fabian Moser

> As for the question of commit access, for me it's a trade-off > between my fear of accidentally breaking something and my wish not > to burden others too often with eventual rebasing/merging chores the > way Jean generously did for me a couple of times. Don't worry ab

Re: Proposing commit access for Lukas-Fabian Moser

Don't worry about breaking something! In almost all cases this gets caught by the CI infrastructure. I think we all agree that it would be very beneficial if you have commit rights. Thanks! So I clicked the "Request access" button yesterday. Should I do anything else? Lukas

Re: Proposing commit access for Lukas-Fabian Moser

Am Samstag, dem 09.10.2021 um 14:42 +0200 schrieb Lukas-Fabian Moser: > > Don't worry about breaking something! In almost all cases this > > gets caught by the CI infrastructure. I think we all agree that it > > would be very beneficial if you have commit rights. > > Thanks! So I clicked the "Re

Re: Proposing commit access for Lukas-Fabian Moser

No, that was the only required step after writing to the mailing list (as documented in the CG), afterwards somebody with Owner permissions (currently Han-Wen and me) have to press the button to accept, which I just did. The complication here is that GitLab doesn't send email notifications that

DOC: Revise CG 3.4 Commit Access (issue 4898058)

LGTM, one suggestion. http://codereview.appspot.com/4898058/diff/1/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): http://codereview.appspot.com/4898058/diff/1/Documentation/contributor/source-code.itexi#newcode1574 Documentation/contributor

Commit access request ( was Re:PATCHES - Countdown for January 10th)

Resending with a more appropriate subject. On Thu, 11 Jan 2018 11:02:20 +0100, Malte Meyn wrote: > Am 10.01.2018 um 18:33 schrieb James Lowe: > > Hello > > > > Here is the current patch countdown list. The next countdown will be on > > January 13th. > > > > […] > > > > Push: > > > > 5247 add

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

LGTM too. My suggestion would be to add some instructions about actually pushing. It took me a while to convince myself that all that appears to be needed is to have an unpushed commit and type "git push". http://codereview.appspot.com/4898058/ ___

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

On 2011/08/18 11:21:22, PhilEHolmes wrote: LGTM too. My suggestion would be to add some instructions about actually pushing. It took me a while to convince myself that all that appears to be needed is to have an unpushed commit and type "git push". Yes, it' s really that simple ;-) We sho

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

http://codereview.appspot.com/4898058/diff/1/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): http://codereview.appspot.com/4898058/diff/1/Documentation/contributor/source-code.itexi#newcode1425 Documentation/contributor/source-code.itexi:1425

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

On 2011/08/18 11:42:13, Reinhold wrote: Documentation/contributor/source-code.itexi:1425: Generate an SSH @q{rsa} key pair. Enter the following at the Why did you change all dsa to rsa? RSA is the older encryption technology, which is known not to be as secure as DSA... Really?! this whol

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Am Friday 19 August 2011, 02:29:22 schrieb percival.music...@gmail.com: > On 2011/08/18 11:42:13, Reinhold wrote: > > Why did you change all dsa to rsa? > > Really?! this whole topic began because somebody said that savannah > requested that people use dsa because it was more secure. It's not on

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

On Fri, Aug 19, 2011 at 03:21:03AM +0200, Reinhold Kainhofer wrote: > Am Friday 19 August 2011, 02:29:22 schrieb percival.music...@gmail.com: > > On 2011/08/18 11:42:13, Reinhold wrote: > > > Why did you change all dsa to rsa? > It's not only savannah, it's basically everone who knows a little bit

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

s up to 4096. Keys of 2048 bits are probably secure for the reasonable future, and are the RSA default. See, for example http://en.wikipedia.org/wiki/Rsa#Security_and_practical_considerations Description: DOC: Revise CG 3.4 Commit Access Please review this at http://codereview.appspot.com/489

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Am Friday, 19. August 2011, 05:11:30 schrieben Sie: > On Fri, Aug 19, 2011 at 03:21:03AM +0200, Reinhold Kainhofer wrote: > > Am Friday 19 August 2011, 02:29:22 schrieb percival.music...@gmail.com: > > > On 2011/08/18 11:42:13, Reinhold wrote: > > > > Why did you change all dsa to rsa? > > > > It'

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

On 2011/08/18 11:42:06, Reinhold wrote: On 2011/08/18 11:21:22, PhilEHolmes wrote: > LGTM too. My suggestion would be to add some instructions about actually > pushing. It took me a while to convince myself that all that appears to be > needed is to have an unpushed commit and type "git pus

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Regarding the addition of instructions on how to push, I'd like to do that in a separate patch, unless an experienced developer cares to send me a rough sketch, point form perhaps, which I could then repackage in documentation format. http://codereview.appspot.com/4898058/ __

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Yes, definitely do the pushing stuff in a separate patch. But here's an outline: 1. update with git pull -r 2. check you only have 1 patch ready with git status 3. upload your changes with git push http://codereview.appspot.com/4898058/ ___ lil

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

2011/8/22 : > Yes, definitely do the pushing stuff in a separate patch.  But here's an > outline: > 1. update with >  git pull -r > 2. check you only have 1 patch ready with >  git status git status shows patches?? Didn't you mean "check that your work is nicely packed in one commit using git log

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Am Monday, 22. August 2011, 09:49:41 schrieben Sie: > Yes, definitely do the pushing stuff in a separate patch. But here's an > outline: > 1. update with >git pull -r > 2. check you only have 1 patch ready with >git status That's the step where I like qgit, because it gives you a really g

Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)

Pushed as 5f81429c8f8263eef85b4f7881d243cb9722e971 Details of how to push will be in a seperate patch. http://codereview.appspot.com/4898058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

doc: Update section on "commit access" (issue 566930043 by jonas.hahnf...@gmail.com)

LGTM https://codereview.appspot.com/566930043/diff/581200043/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot.com/566930043/diff/581200043/Documentation/contributor/source-code.itexi#newcode2196 Documentation/contri

Re: doc: Update section on "commit access" (issue 566930043 by jonas.hahnf...@gmail.com)

On 2019/10/24 19:05:49, lemzwerg wrote: LGTM https://codereview.appspot.com/566930043/diff/581200043/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot.com/566930043/diff/581200043/Documentation/contributor/sourc

Re: doc: Update section on "commit access" (issue 566930043 by jonas.hahnf...@gmail.com)

Thanks for the corrections. https://codereview.appspot.com/566930043/diff/551130043/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot.com/566930043/diff/551130043/Documentation/contributor/source-code.itexi#newcode22

Re: doc: Update section on "commit access" (issue 566930043 by jonas.hahnf...@gmail.com)

LGTM https://codereview.appspot.com/566930043/

Doc: CG - Minor updates to 3.4.9 - Commit access (issue 566540043 by pkxgnugi...@runbox.com)

It's too long I had to follow those lines, thus I can't say anything to your changes. One nit: https://codereview.appspot.com/566540043/diff/566530044/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot.com/566540043/

Re: Doc: CG - Minor updates to 3.4.9 - Commit access (issue 566540043 by pkxgnugi...@runbox.com)

I guess that most GNOME users nowadays use version 3, so we should use the gsettings command instead of GConf. https://codereview.appspot.com/566540043/diff/566530044/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot

Re: Doc: CG - Minor updates to 3.4.9 - Commit access (issue 566540043 by pkxgnugi...@runbox.com)

This looks good to me, except a phrasing nitpick. https://codereview.appspot.com/566540043/diff/566530044/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): https://codereview.appspot.com/566540043/diff/566530044/Documentation/contributor/sourc