Try -O as an option in your scp cmd, i.e. scp -p -O -P 29418 [email protected]:hooks/commit-msg “jyei-erp/.git/hooks/” Faced similar issue. This solution is from comments in github regarding this problem. For more details – https://github.com/PowerShell/Win32-OpenSSH/issues/1945
Try -O as an option in your scp cmd, i.e. scp -p -O -P 29418 [email protected]:hooks/commit-msg “jyei-erp/.git/hooks/” Faced similar issue. This solution is from comments in github regarding this problem. For more details – https://github.com/PowerShell/Win32-OpenSSH/issues/1945
Notice: Since this question was origionally asked, I’ve released the delete project plugin, and handed it off to the more active Gerrit devs. If you are using Gerrit >= 2.7, I’d recommend this route. If not, read on. There isn’t a method to delete projects from Gerrit currently. It must be done by hand. This … Read more
you need to reconfigure your email $ git config user.email <your email> $ git commit –amend –reset-author git commit –amend updates your last commits
You can specify multiple ranges: git cherry-pick A..B C..D E..F or even specific commits: git cherry-pick A B C D E F If you have lots of commits you want to exclude, it might be easier to do something like this (sort of like a poor man’s git rebase -i for git cherry-pick): git log … Read more
Gerrit is it’s own server and the issues we’ve seen were with the client and have recently been fixed in the brand new version of JGit. It also didn’t corrupt the repository, it just pushed packfiles that were missing objects. The Gerrit server is solid and has been used by the Android project for over … Read more
Use git push –no-thin instead of git push. From Git docs: A thin transfer significantly reduces the amount of sent data when the sender and receiver share many of the same objects in common. The default is –thin.
This situation has been reported as a bug in Gerrit. Here’s a solution/workaround from Gerrit’s issue tracker: To the best of my knowledge, you have 2 options currently – Force push to refs/heads. It is just a fast-forward, so in theory everything has already been reviewed and verified. There is no point in doing so … Read more
This issue is due to the actions I’d performed previously. I was trying to push a new change, on top of a change which was still up for review, who’s parent also was up for review. Trunk —— Parent A —– Parent B —– New change (merged) (unmerged) (unmerged) I had used cherry-pick to obtain … Read more
No, sorry, this is not currently possible. The design assumes that the most recent patch set is the one developers will review and test, and as such older patch sets can not be submitted. They also can not be reviewed/verified. If you want to use an older version of a patch set, you must re-submit … Read more