From 29ee4436531f2f7e33b8d8f899589709bbdc2f59 Mon Sep 17 00:00:00 2001
From: Jacob Keller <jacob.e.keller@intel.com>
Date: Tue, 11 Aug 2015 16:09:34 -0700
Subject: [PATCH] email: update message on autodetect project failure

Update the message so that it is more clear why git-find-base fails
generally. The most common case is patches based on work which is not
yet applied by the maintainer. The previous message did not make this
clear, and thus users were confused.

Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
---
 email/aiaiai-email-autodetect-project | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/email/aiaiai-email-autodetect-project b/email/aiaiai-email-autodetect-project
index 6e832a4..465f6c2 100755
--- a/email/aiaiai-email-autodetect-project
+++ b/email/aiaiai-email-autodetect-project
@@ -147,11 +147,12 @@ else
 	cat "$tmp_find_base" 1>&2
 
 	cat <<EOF
-Aiaiai was unable to correctly determine the project for your patch submission.
-Normally the diff index information provided by git's diff mechanism is enough.
-The most probably cause is that your patch is based against an older reference
-to the project, and you need to rebase your submission against the current
-tree.
+Aiaiai was not able to automatically determine the project for your patch
+submission using the index information provided by git-diff. This can be caused
+because your patch is based on work which is not yet applied to the queue, or
+if your patch is based on a really old version of the queue. You might try to
+rebase your submission and re-submit against the current development
+queue.
 EOF
 	exit 127
 	fi
-- 
2.49.0