-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Issues in PEAR repository and after it, detach the fork from upstream to have main code #2
Comments
@CloCkWeRX thoughts? |
Or: in few minutes (harmonize when to do it):
After, all people are happy ^^ |
Dear all, it is possible to detach https://github.com/pear/Auth_SASL2 from https://github.com/CloCkWeRX/Auth_SASL2? Request must be done here: Thanks in advance. |
@CloCkWeRX , maybe the easiest path here would be for you to delete your |
@ashnazg: Badly, after this repo removal, another one can be upstream too... Better solution: It is to detach the PEAR repository with a request here: To have only: https://github.com/pear/Auth_SASL2/ And it is needed to work on master branch to see that it always developed... cc: @schengawegga. |
Dear @pear team, @jparise, and current contributors: @ashnazg,@CloCkWeRX, @troymccabe, @kenguest, @cweiske, @mj, @till, @Jehan,
In first, I wish you a Happy New Year 2022!
It is possible to add "Issues" section into the pear source repository?
Can you detach the upstream repository from the original place: https://github.com/CloCkWeRX/Auth_SASL2?
The goal is to have the main source code in PEAR organization like, for example:
Thanks in advance.
PS: If @CloCkWeRX removes this repository, it will be directly good about the second part.
The text was updated successfully, but these errors were encountered: