packaging: Document how amending an arc diff prompts for input

When using arc diff on an existing diff that is being amended, the
user is requested to add some information. Document this so that they
don't feel lost and have a reference to turn to.

Signed-off-by: Ikey Doherty <ikey@solus-project.com>
This commit is contained in:
Ikey Doherty 2017-05-07 00:29:07 +01:00
parent da3c51216c
commit 3930175173
No known key found for this signature in database
GPG Key ID: 78E2387015C1205F
1 changed files with 6 additions and 2 deletions

View File

@ -102,8 +102,12 @@ before, but this time run:
git commit --amend git commit --amend
``` ```
This will amend your original changes, and you can submit the patch once more with `arc diff`. The web UI will This will amend your original changes, and you can submit the patch once more with `arc diff`.
automatically update with the latest patch, without having to create any new tasks. Once accepted, your patch A new editor session will open, where you can provide details about the changes you've made between the last
revision and the newly amended one. This comment will help reviewers to see what you've changed, to streamline
the process of getting your patch into Solus.
The web UI will automatically update with the latest patch, without having to create any new tasks. Once accepted, your patch
will be merged, and a build will be issued. will be merged, and a build will be issued.