Meta/cook: update explanation of next and seen

index 4ac942c594..d477bab540 100755 --- a/cook +++ b/cook @@ -288,16 +288,15 @@ sub blurb_text { $next_at ||= '0' x 40; $text ||= <<'EOF'; Here are the topics that have been cooking in my tree. Commits -prefixed with '-' are only in 'seen' while commits prefixed with '+' -are in 'next'. The ones marked with '.' do not appear in any of the -integration branches, but I am still holding onto them. Generally, -being in 'next' is a sign that a topic is stable enough to be used -and are candidate to be in a future release, while being in 'seen' -means nothing more than that the maintainer has found it interesting -for some reason (like "it may have hard-to-resolve conflicts with +prefixed with '+' are in 'next' (being in 'next' is a sign that a +topic is stable enough to be used and are candidate to be in a +future release). Commits prefixed with '-' are only in 'seen', +which means nothing more than that I have found them of interest for +some reason (like "it may have hard-to-resolve conflicts with another topic already in flight" or "this may turn out to be -useful")---do not read too much into a topic being in (or not in) -'seen'. +useful"). Do not read too much into a topic being in (or not in) +'seen'. The ones marked with '.' do not appear in any of the +integration branches, but I am still holding onto them. Copies of the source code to Git live in many repositories, and the