The "I have submitted a patch" automatic mail from gerrit currently contains: To pull it, you can do: git pull ssh://gerrit.libreoffice.org:29418/core refs/changes/15/3615/1 Please make that: To pull it, you can do: git pull git://gerrit.libreoffice.org/core refs/changes/15/3615/1 So that this command-line works anywhere, anytime, not only when one has properly setup ssh authentication to gerrit on the currently used machine. (My personal case is that I usually have not introduced my crypto smartcard for authentication.)
(In reply to comment #0) > The "I have submitted a patch" automatic mail from gerrit currently contains: > > > To pull it, you can do: > > git pull ssh://gerrit.libreoffice.org:29418/core refs/changes/15/3615/1 > > > Please make that: > > > To pull it, you can do: > > git pull git://gerrit.libreoffice.org/core refs/changes/15/3615/1 > > > So that this command-line works anywhere, anytime, not only when one has > properly setup ssh authentication to gerrit on the currently used machine. > (My personal case is that I usually have not introduced my crypto smartcard > for authentication.) Lionel - Is this still a problem? I find a few gerrit emails from last September that mention an ssh:// url, but perhaps the problem has been fixed between then and now?
(In reply to comment #1) > Lionel - Is this still a problem? Yes, it is. > I find a few gerrit emails from last > September (...) perhaps the problem has been fixed > between then and now? No, it has not.
Let's do it.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
ticket moved to redmine, see https://redmine.documentfoundation.org/issues/1549