On Mon, Apr 03, 2017 at 03:56:45PM -0700, Frank Filz wrote: ... > You can find it in my readahead branch: > > https://github.com/ffilz/nfs-ganesha/commits/readahead > > Or review on gerrithub: > > https://review.gerrithub.io/#/c/355552/ > https://review.gerrithub.io/#/c/355563/ > https://review.gerrithub.io/#/c/355564/ > https://review.gerrithub.io/#/c/355565/ > > You can also pull the whole branch from gerrithub with this command (which > will create and checkout a branch called readahead in your repo): > > git fetch https://ff...@review.gerrithub.io/a/ffilz/nfs-ganesha > refs/changes/65/355565/1 && git checkout FETCH_HEAD -b readahead > > This last is taken from the download menu in the final patch, you chose the > checkout option, cut and paste that. I always add the -b {branchname} to the > end of it to actually checkout a branch. This can be used to pull down > anyone's patch set even if they don't have a github repo (or you don't know > what it is, or they didn't push to it). I use this all the time for doing > weekly merges if someone has a patchset with more than 2 or 3 patches.
Or you can install the git-review package (which you most likely already have anyway), and run the following command in your repository: $ git review -d 355565 This will create a new branch to review the patch series. The effect is the same as with the fancy 'git fetch ....' command, this is just a little shorter ;-) You can also use 'git review -x <CHANGE_ID>' to cherry pick a change(set) in your current working branch. HTH, Niels
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
