Re: [GitHub] Your password was reset
just wondering if there's something going on? Is there a github account associated with the mailing list email? seems odd... GitHub escreveu no dia domingo, 26/08/2018 à(s) 10:35: > > Hello amc2399, > > We wanted to let you know that your GitHub password was reset. > > If you did not perform this action, you can recover access by entering > git@vger.kernel.org into the form at https://github.com/password_reset > > To see this and other security events for your account, visit > https://github.com/settings/security > > If you run into problems, please contact support by visiting > https://github.com/contact > > Please do not reply to this email with your password. We will never ask for > your password, and we strongly discourage you from sharing it with anyone. -- Obrigado, Pedro Rijo
Re: hacktoberfest
seems my last answer was blocked due to HTML :( here's the answer: Seems a nice start yes. I've been on vacations, but next week I will go trough the current issues and add the hacktoberfest label to some issues if you agree. I went through the open issues a few moments ago. Some were closed (solved or not applicable anymore), and some got an hacktoberfest label, hoping new contributors pop up. Feel free to have a look and add new issues to the label, as well as remove some of those I thought it could be a good fit. There are easy issue, and some not so easy (not very hard, but a bit more work) probably. Issues labeled: https://github.com/git/git-scm.com/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest Thanks, Pedro 2017-09-28 22:19 GMT+01:00 Jeff King <p...@peff.net>: > On Wed, Sep 27, 2017 at 11:05:49PM +0100, pedro rijo wrote: > >> While the git repository itself is not hosted under GitHub, the Pro >> Git book, git for Windows, and git-scm website (at least) projects >> are, and could use this movement to get some more contributions, and >> eventually more maintainers (at least git-scm website had some >> maintainers problem some time ago). >> >> I've been helping on the git-scm repository (mostly filtering issues >> and PRs), and I know there are still some issues which need to be >> addressed. If the remaining maintainers agree, we could filter and >> provide more instructions to some easy (or not so easy) issues, adding >> the 'hacktoberfest' label and try to use this movement to solve some >> problems > > I'd love it if more people wanted to contribute to the git-scm > repository. I think one can probably find some low-hanging fruit by > looking at the open issues list (though I'd be happy, too, if people > with bug or feature suggestions opened new issues). > > Here are a couple small-to-moderate bugs that have been languishing: > > https://github.com/git/git-scm.com/issues/701 > > https://github.com/git/git-scm.com/issues/987 > > https://github.com/git/git-scm.com/issues/994 > > -Peff -- Obrigado, Pedro Rijo
hacktoberfest
Hey, As some may have noticed, GitHub and DigitalOcean have been promoting Open Source contributions in October for a few years now. While the git repository itself is not hosted under GitHub, the Pro Git book, git for Windows, and git-scm website (at least) projects are, and could use this movement to get some more contributions, and eventually more maintainers (at least git-scm website had some maintainers problem some time ago). I've been helping on the git-scm repository (mostly filtering issues and PRs), and I know there are still some issues which need to be addressed. If the remaining maintainers agree, we could filter and provide more instructions to some easy (or not so easy) issues, adding the 'hacktoberfest' label and try to use this movement to solve some problems Probably, other repositories could also enjoy the opportunity. Here's the website: https://hacktoberfest.digitalocean.com/ -- Thanks, Pedro
Re: [BUG] Failed to sign commit
as much cliché as it may seem, GPG was with some strange behaviour, killing the agent and starting again make it work with no problems Thanks for the help 2017-06-07 21:41 GMT+01:00 Bryan Turner <btur...@atlassian.com>: >> $ GIT_TRACE=1 git commit --allow-empty -v -m "lol" >> 11:37:24.594795 git.c:369 trace: built-in: git 'commit' >> '--allow-empty' '-v' '-m' 'lol' >> 11:37:24.605842 run-command.c:369 trace: run_command: 'gpg' >> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E' >> error: gpg failed to sign the data >> fatal: failed to write commit object >> >> It seems more a gpg problem no? something not well configured after >> the update perhaps? > > Have you tried running `export GPG_TTY=$(tty)` before running `git > commit`? I had a similar gpg error that was solved by that. -- Obrigado, Pedro Rijo
Re: [BUG] Failed to sign commit
Thanks for the hint! $ GIT_TRACE=1 git commit --allow-empty -v -m "lol" 11:37:24.594795 git.c:369 trace: built-in: git 'commit' '--allow-empty' '-v' '-m' 'lol' 11:37:24.605842 run-command.c:369 trace: run_command: 'gpg' '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E' error: gpg failed to sign the data fatal: failed to write commit object It seems more a gpg problem no? something not well configured after the update perhaps? 2017-06-07 11:33 GMT+01:00 Kevin Daudt <m...@ikke.info>: > On Wed, Jun 07, 2017 at 10:46:08AM +0100, pedro rijo wrote: >> Recently I've updated a bunch of stuff, including git and gpg. I'm using >> >> - mac OS 10.10.5 >> - git 2.13.1 >> - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7 >> >> When I do >> >> $ git commit --allow-empty -v -m "lol" >> error: gpg failed to sign the data >> fatal: failed to write commit object >> >> I tried the verbose flag hoping to have a better insight, but not very >> useful. Not sure if it's a gpg problem, a git problem, or something >> else. >> >> Any clue on how to debug the problem? Do you need any gpg output to >> better understand the problem? >> >> Thanks, >> Pedro > > GIT_TRACE=1 git commit --allow-empty -v -m "lol" might give some extra > feedback (ie, what gpg command git runs), and try to see if you can > replicate it. -- Obrigado, Pedro Rijo
[BUG] Failed to sign commit
Recently I've updated a bunch of stuff, including git and gpg. I'm using - mac OS 10.10.5 - git 2.13.1 - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7 When I do $ git commit --allow-empty -v -m "lol" error: gpg failed to sign the data fatal: failed to write commit object I tried the verbose flag hoping to have a better insight, but not very useful. Not sure if it's a gpg problem, a git problem, or something else. Any clue on how to debug the problem? Do you need any gpg output to better understand the problem? Thanks, Pedro
Re: meaning of SP on ls-tree docs
ups :) Thanks 2016-04-11 18:15 GMT+01:00 Konstantin Khomoutov <kostix+...@007spb.ru>: > On Mon, 11 Apr 2016 18:04:42 +0100 > pedro rijo <pedrorij...@gmail.com> wrote: > >> On https://git-scm.com/docs/git-ls-tree#_output_format, the format is >> presented as SP SP TAB >> >> But what is SP? Couldn't find the meaning. Space? System separator? > > A single space character, code 0x20 in HEX or 32 in decimal. > TAB is a single TAB character, code 9. -- Obrigado, Pedro Rijo -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
meaning of SP on ls-tree docs
Hey, On https://git-scm.com/docs/git-ls-tree#_output_format, the format is presented as SP SP TAB But what is SP? Couldn't find the meaning. Space? System separator? -- Thanks, Pedro Rijo -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
