Hi Jörg, It is in the upper right corner. The links are pretty small. You are not the first who missed them. :-)
Cheers, Balint 2014-01-28 Joerg Mayer <jma...@loplof.de>: > Looks like I'm blind. Where do I create the account? > > Thanks > Jörg > > On Tue, Jan 14, 2014 at 09:28:08PM -0500, Evan Huus wrote: >> I have created an account and added an SSH key, but I am getting >> "Permission denied (publickey)" when trying to clone. Is it working >> for anyone else? >> >> On Tue, Jan 14, 2014 at 4:50 PM, Gerald Combs <ger...@wireshark.org> wrote: >> > The live Gerrit site is up and running at >> > https://code.wireshark.org/review. At this point you should be able to >> > do the following: >> > >> > - Create an account[1]. This includes adding SSH keys, adding >> > OpenID identities, and setting an HTTP password. >> > >> > - Clone the repository anonymously or using your ID: >> > https://code.wireshark.org/review/wireshark >> > ssh://your.usern...@code.wireshark.org:29418/wireshark >> > https://your.usern...@code.wireshark.org/review/wireshark >> > >> > - Push changes to a Gerrit magic ref[2] (e.g. >> > HEAD:refs/for/master/convert-packets-to-frozen-custard). >> > >> > Please be careful about pushing to non-magic, normal Git refs. It >> > *shouldn't* be possible to do so but if it does happen it could result >> > in a merge conflict. >> > >> > I'm mirroring the Gerrit repository directly from the current git >> > repository, i.e. behind Gerrit's back. This is non-standard but *should* >> > be safe as long as no commits are done on the Gerrit side. >> > >> > Most of the buildbots now check out source code using git. I'll probably >> > have them all migrated in the next day or so. >> > >> > The weekly automatic number update script has been migrated to git. It >> > successfully pushed to the test repository and should push to the live >> > repository this upcoming Sunday. >> > >> > The data for the OUI lookup tool >> > (http://www.wireshark.org/tools/oui-lookup.html) now comes from git. >> > >> > >> > Next steps: >> > >> > - Update make-version.pl. >> > >> > - Update the web site and wiki documentation. >> > >> > - Further Buildbot integration. We should be able to do test builds >> > as part of the review process but that will likely have to wait >> > until after the migration. >> > >> > >> > Questions: >> > >> > When should we schedule flag day? Is two weeks from now (Jan 28) too >> > soon? I don't want to stretch the migration out too long but I also want >> > to give everyone time to get set up and settled in. >> > >> > Is it safe to redirect Git repositories served over HTTP? If so I'll >> > likely redirect http://code.wireshark.org/git/wireshark to >> > https://code.wireshark.org/review/wireshark after the migration. >> > >> > >> > Links: >> > >> > [1]: http://test.code.wireshark.org/review/Documentation/intro-quick.html >> > >> > [2]: >> > http://test.code.wireshark.org/review/Documentation/user-upload.html#push_create >> > ___________________________________________________________________________ >> > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> > Archives: http://www.wireshark.org/lists/wireshark-dev >> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > -- > Joerg Mayer <jma...@loplof.de> > We are stuck with technology when what we really want is just stuff that > works. Some say that should read Microsoft instead of technology. > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
