I haven't used it, but git cola seems to be a GUI that supports custom 
commands: http://git-cola.github.io

So you should just be able to add buttons for running "git review" et al.

> On Mar 11, 2014, at 11:00 PM, mman...@netscape.net wrote:
> 
> My biggest frustration is noted by the statement:
>  
> "However, as most use on other platforms tends to be command-line git, most 
> books and guides tend to concentrate on that so windows users may actually 
> find it easier to start with the command line and then move to graphical 
> clients when they are comfortable with the basics."
>  
> I didn't really want to learn the command line, I like GUIs :)  TortoiseSVN 
> did a great job of hiding the underlying commandline from me and since I 
> never did anything advanced with it, it served me well.  TortoiseGit hasn't 
> succeeded as well for me and I'm still battling with it in an effort to not 
> have to use the commandline at all (it's this "tutorial" I assume most 
> Windows developers are after, because I certainly am)
>  
> I think most of my issues are being caused by Gerrit and the extra "path" 
> required on a push.  TortoiseGit appears to have answers for it, but trying 
> to tackle all three at once (git + Gerrit + TortoiseGit) is a bit much to 
> chew on when all references are commandline.
>  
>  
> -----Original Message-----
> From: Graham Bloice <graham.blo...@trihedral.com>
> To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
> Sent: Tue, Mar 11, 2014 6:04 pm
> Subject: Re: [Wireshark-dev] Fix bug in GSM MAP, have problems with GIT
> 
> 
>  
> Initial stab at this is up now: 
> http://wiki.wireshark.org/Development/SubmittingPatches/GitForWindows 
> 
> This is based purely on what I did to get up and running, not quite finished 
> yet, and it is very PowerShell oriented (because that is the one true way 
> forward!).  Feel free to hack it about.
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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

Reply via email to