Thanks for your help. Regards. Krishna Harathi
On Sun, Jul 26, 2015 at 11:46 AM, Niels de Vos <nde...@redhat.com> wrote: > On Sun, Jul 26, 2015 at 11:00:29AM -0700, Krishna Harathi wrote: > > Can someone point me to a fix submission process document or a summary? > > > > I looked at Ganesha wiki as well as read some past email. I came across > > some recent > > email from Frank and others on this subject, but I am not clear on the > > process. > > I think this is the page and section that should help you: > > > https://github.com/nfs-ganesha/nfs-ganesha/wiki/DevPolicy#patch-submission-guidelines > > Basically, you need to create an account (with your GitHub credentials) > on http://gerrithub.io and add a public ssh-key in your account > settings. After that, you should clone (or add the remote) based on this > URL > > $ git clone ssh://${ > GITHUB_USERNAME}@review.gerrithub.io:29418/ffilz/nfs-ganesha > > Patches are sent against the "next" branch, and it is easiest to create > one branch per patch(-series): > > $ git checkout -t -b my-fixes-for-foo origin/next > > Once you have committed and tested your changes, you can push them to > gerrithub. I prefer to use the git-review tool for that: > > $ git review -t my-fixes-for-foo > > This posts the commits to gerrithub, and will show you the URLs where > you and others can review the changes. > > Good luck! > Niels >
------------------------------------------------------------------------------
_______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
