You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2024. It is now read-only.
As an end-user command-line tool for testing patches, skt doesn't really need to send testing results anywhere and can just output them to stdout. If we move report sending to sktm, skt won't need to know anything about Patchwork (can work with just patch URLs), or things like Message-IDs to put in In-Reply-To.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an end-user command-line tool for testing patches, skt doesn't really need to send testing results anywhere and can just output them to stdout. If we move report sending to sktm, skt won't need to know anything about Patchwork (can work with just patch URLs), or things like Message-IDs to put in In-Reply-To.
The text was updated successfully, but these errors were encountered: