-
Notifications
You must be signed in to change notification settings - Fork 333
Question: What is the intended sharing process with upstream? #471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You can see some of the efforts in merging to upstream at https://github.com/openssh/openssh-portable/pulls?q=+is%3Apr+author%3Amanojampalam+. Most notably is the large PR openssh#63 that was rejected for being too Windows specific so alot of changes were made to try to minimize impact to upstream. I haven't seen any status updates in awhile. The last update I saw was on the wiki https://github.com/PowerShell/Win32-OpenSSH/wiki/Project-Status |
@GitMensch - We have a strong desire to get our changes upstream. We tried couple of times to get our changes but they got rejected as they are very specific to windows. Our priorities have changed over the time to invest in other projects. |
We track issues in a different repo https://github.com/PowerShell/Win32-OpenSSH/issues. |
As this was a question - going on with PowerShell/Win32-OpenSSH#2257. |
Obviously many of the code changes would be relevant to be placed upstream - is there any plan to do send PRs?
Even more obviously this repo tends to get outdated, what are the plans on pulling OpenSSH 8,1-8,4 here?
I thought to find the information in one of the repo's README or the Wiki - but had no luck with this.
The text was updated successfully, but these errors were encountered: