[PATCH] fetch: improve grammar of "shallow roots" message

Subsystems: the rest

STALE1910d

5 messages, 3 authors, 2021-05-20 · open the first message on its own page

[PATCH] fetch: improve grammar of "shallow roots" message

From: Alex Henrie <hidden>
Date: 2021-05-18 06:19:03

Signed-off-by: Alex Henrie <redacted>
---
 builtin/fetch.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/fetch.c b/builtin/fetch.c
index 97c4fe6e6d..c19a041526 100644
--- a/builtin/fetch.c
+++ b/builtin/fetch.c
@@ -1123,7 +1123,7 @@ static int store_updated_refs(const char *raw_url, const char *remote_name,
 
 			if (rm->status == REF_STATUS_REJECT_SHALLOW) {
 				if (want_status == FETCH_HEAD_MERGE)
-					warning(_("reject %s because shallow roots are not allowed to be updated"),
+					warning(_("rejected %s because shallow roots are not allowed to be updated"),
 						rm->peer_ref ? rm->peer_ref->name : rm->name);
 				continue;
 			}
-- 
2.31.1

Re: [PATCH] fetch: improve grammar of "shallow roots" message

From: Derrick Stolee <hidden>
Date: 2021-05-19 13:55:45

On 5/18/2021 2:18 AM, Alex Henrie wrote:
- warning(_("reject %s because shallow roots are not allowed to be updated"),
+ warning(_("rejected %s because shallow roots are not allowed to be updated"),
This change to past-tense makes sense to me.

Thanks,
-Stolee

Re: [PATCH] fetch: improve grammar of "shallow roots" message

From: Bagas Sanjaya <hidden>
Date: 2021-05-20 02:22:35

On 18/05/21 13.18, Alex Henrie wrote:
-					warning(_("reject %s because shallow roots are not allowed to be updated"),
+					warning(_("rejected %s because shallow roots are not allowed to be updated"),
 From descriptive to null-subject past tense, right?

-- 
An old man doll... just what I always wanted! - Clara

Re: [PATCH] fetch: improve grammar of "shallow roots" message

From: Alex Henrie <hidden>
Date: 2021-05-20 04:02:38

On Wed, May 19, 2021 at 8:22 PM Bagas Sanjaya [off-list ref] wrote:
On 18/05/21 13.18, Alex Henrie wrote:
quoted
-                                     warning(_("reject %s because shallow roots are not allowed to be updated"),
+                                     warning(_("rejected %s because shallow roots are not allowed to be updated"),
 From descriptive to null-subject past tense, right?
I'm not sure what the best way is to describe the grammar here. I
would say that the "ed" makes it clear that the message is a
description of what did happen rather than an imperative command
concerning what should happen.

-Alex

Re: [PATCH] fetch: improve grammar of "shallow roots" message

From: Bagas Sanjaya <hidden>
Date: 2021-05-20 05:03:42

On 20/05/21 11.02, Alex Henrie wrote:
On Wed, May 19, 2021 at 8:22 PM Bagas Sanjaya [off-list ref] wrote:
quoted
On 18/05/21 13.18, Alex Henrie wrote:
quoted
-                                     warning(_("reject %s because shallow roots are not allowed to be updated"),
+                                     warning(_("rejected %s because shallow roots are not allowed to be updated"),
  From descriptive to null-subject past tense, right?
I'm not sure what the best way is to describe the grammar here. I
would say that the "ed" makes it clear that the message is a
description of what did happen rather than an imperative command
concerning what should happen.

-Alex
Looks OK.

So the error had happened, and we needed to express the situation.
Because it happened on the past, using past tense was obviously the
right thing.

Reviewed-by: Bagas Sanjaya <redacted>

-- 
An old man doll... just what I always wanted! - Clara
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help