Meta/cook: update explanation of next and seen
Junio C Hamano committed
Jul 8, 2021 at 14:10 UTC
e2d17bdce0def16c8ded1cd88bc182f99fb61112
1 file changed
+8
-9
cook
+8
-9
@@ -288,16 +288,15 @@ sub blurb_text {
288
$next_at ||= '0' x 40;
289
$text ||= <<'EOF';
290
Here are the topics that have been cooking in my tree. Commits
291
-prefixed with '-' are only in 'seen' while commits prefixed with '+'
292
-are in 'next'. The ones marked with '.' do not appear in any of the
293
-integration branches, but I am still holding onto them. Generally,
294
-being in 'next' is a sign that a topic is stable enough to be used
295
-and are candidate to be in a future release, while being in 'seen'
296
-means nothing more than that the maintainer has found it interesting
297
-for some reason (like "it may have hard-to-resolve conflicts with
291
+prefixed with '+' are in 'next' (being in 'next' is a sign that a
292
+topic is stable enough to be used and are candidate to be in a
293
+future release). Commits prefixed with '-' are only in 'seen',
294
+which means nothing more than that I have found them of interest for
295
+some reason (like "it may have hard-to-resolve conflicts with
296
another topic already in flight" or "this may turn out to be
299
-useful")---do not read too much into a topic being in (or not in)
300
-'seen'.
297
+useful"). Do not read too much into a topic being in (or not in)
298
+'seen'. The ones marked with '.' do not appear in any of the
299
+integration branches, but I am still holding onto them.
300
301
302
Copies of the source code to Git live in many repositories, and the