I used git-review too, it is provide by Python on Windows. All I need to do is to commit via SmartGit and then type in "git-review".
On Tue, Apr 19, 2016 at 7:52 PM, Graham Bloice <[email protected]> wrote: > I find using the git-review ( > https://www.mediawiki.org/wiki/Gerrit/git-review) tool simplifies a lot > of Gerrit\git interactions. > > On 19 April 2016 at 12:44, Yang Luo <[email protected]> wrote: > >> Hi all, >> >> I found I can push using https, but the reminds me it lacks change-id. >> I fnished cloning via https and got this done:) >> >> My patch is: >> https://code.wireshark.org/review/#/c/15003/ >> >> Thanks for your help! >> >> Cheers, >> Yang >> >> >> >> On Tue, Apr 19, 2016 at 7:26 PM, Dario Lombardo < >> [email protected]> wrote: >> >>> To push using ssh (that is one of the two methods supported) you have to >>> upload your public key to gerrit using the web interface. Next to the http >>> section, you can find the ssh one. Use it to upload the key. >>> >>> You can push using http and its password. Simply replace the ssh url >>> with the https one. >>> >>> On Tue, Apr 19, 2016 at 1:02 PM, Yang Luo <[email protected]> wrote: >>> >>>> Hi Dario, >>>> >>>> I got this error. >>>> >>>> J:\github_repos\wireshark>git push ssh:// >>>> [email protected]:29418/wireshark >>>> HEAD:refs/for/master/dot11-support-on-windows >>>> Permission denied (publickey). >>>> fatal: Could not read from remote repository. >>>> >>>> Please make sure you have the correct access rights >>>> and the repository exists. >>>> >>>> >>>> On Tue, Apr 19, 2016 at 6:35 PM, Dario Lombardo < >>>> [email protected]> wrote: >>>> >>>>> Hi Yang >>>>> You can clone from github, then add whatever git remote you want. But >>>>> you don't need to do that, since the command to push a change to gerrit >>>>> can >>>>> be issued to point directly to wireshark repo. As stated here >>>>> https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html >>>>> you can push to >>>>> >>>>> git push ssh://[email protected]:29418/wireshark >>>>> HEAD:refs/for/master/snowcone-machine >>>>> >>>>> so >>>>> >>>>> git clone <github> >>>>> [changes] >>>>> git push ssh://[email protected]:29418/wireshark >>>>> HEAD:refs/for/master/snowcone-machine >>>>> >>>>> OR >>>>> >>>>> git clone <github> >>>>> git add remote wsrepo ssh:// >>>>> [email protected]:29418/wireshark >>>>> [changes] >>>>> git push wsrepo HEAD:refs/for/master/snowcone-machine >>>>> >>>>> Be careful to check that the github repo is aligned to master as you >>>>> expect. >>>>> >>>>> But if you're experiencing problems downloading from wireshark, it is >>>>> very likely that you will have issues uploading to it. >>>>> Dario. >>>>> >>>>> On Tue, Apr 19, 2016 at 10:45 AM, Yang Luo <[email protected]> wrote: >>>>> >>>>>> Hi list, >>>>>> >>>>>> I want to submit a patch to Wireshark. I'm using SmartGit on Win10. >>>>>> My location is Beijing. I followed the guide here: >>>>>> https://wiki.wireshark.org/Development/SubmittingPatches >>>>>> >>>>>> And I always fails this step: >>>>>> git clone ssh://[email protected]:29418/wireshark >>>>>> Because the speed is 20KB/s to 40KB/s, and and downloading a half >>>>>> more or less the connection usually fails. >>>>>> >>>>>> I can download the code from GitHub: >>>>>> git clone https://github.com/wireshark/wireshark >>>>>> it's speed is 200KB/s +. >>>>>> >>>>>> I want to know if there a way to make Wireshark's GitHub repo able to >>>>>> commit to gerrit, or change the GitHub repo into the Gerrit recognized >>>>>> repo, or download the repo in a "continue transferring from breakpoint" >>>>>> way? >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Yang >>>>>> >>>>>> >>>>>> ___________________________________________________________________________ >>>>>> Sent via: Wireshark-dev mailing list <[email protected]> >>>>>> Archives: https://www.wireshark.org/lists/wireshark-dev >>>>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >>>>>> mailto:[email protected] >>>>>> ?subject=unsubscribe >>>>>> >>>>> >>>>> >>>>> >>>>> ___________________________________________________________________________ >>>>> Sent via: Wireshark-dev mailing list <[email protected]> >>>>> Archives: https://www.wireshark.org/lists/wireshark-dev >>>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >>>>> mailto:[email protected] >>>>> ?subject=unsubscribe >>>>> >>>> >>>> >>>> >>>> ___________________________________________________________________________ >>>> Sent via: Wireshark-dev mailing list <[email protected]> >>>> Archives: https://www.wireshark.org/lists/wireshark-dev >>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >>>> mailto:[email protected] >>>> ?subject=unsubscribe >>>> >>> >>> >>> >>> ___________________________________________________________________________ >>> Sent via: Wireshark-dev mailing list <[email protected]> >>> Archives: https://www.wireshark.org/lists/wireshark-dev >>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >>> mailto:[email protected] >>> ?subject=unsubscribe >>> >> >> >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <[email protected]> >> Archives: https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:[email protected] >> ?subject=unsubscribe >> > > > > -- > Graham Bloice > Software Developer > Trihedral UK Limited > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected] > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
