From 39301751736fc585829239cd33ca496da7c8d666 Mon Sep 17 00:00:00 2001 From: Ikey Doherty Date: Sun, 7 May 2017 00:29:07 +0100 Subject: [PATCH] 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 --- packaging/submitting-a-package/en.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/packaging/submitting-a-package/en.md b/packaging/submitting-a-package/en.md index 1e51dac..e730e73 100644 --- a/packaging/submitting-a-package/en.md +++ b/packaging/submitting-a-package/en.md @@ -102,8 +102,12 @@ before, but this time run: git commit --amend ``` -This will amend your original changes, and you can submit the patch once more with `arc diff`. The web UI will -automatically update with the latest patch, without having to create any new tasks. Once accepted, your patch +This will amend your original changes, and you can submit the patch once more with `arc diff`. +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.