Meta/cook: order the source URLs stably
Junio C Hamano committed
Sep 9, 2022 at 15:12 UTC
276d31029f66a4ad7b8e70bf264ab85a4e101d42
1 file changed
+5
-10
cook
+5
-10
@@ -158,7 +158,7 @@ sub get_source {
158
map {
159
" source: <$_>";
160
}
161
- (keys %source);
161
+ (sort keys %source);
162
}
163
164
sub reduce_sources {
@@ -381,15 +381,10 @@ sub blurb_text {
381
$text ||= <<'EOF';
382
Here are the topics that have been cooking in my tree. Commits
383
prefixed with '+' are in 'next' (being in 'next' is a sign that a
384
-topic is stable enough to be used and are candidate to be in a
385
-future release). Commits prefixed with '-' are only in 'seen',
386
-which means nothing more than that I have found them of interest for
387
-some reason (like "it may have hard-to-resolve conflicts with
388
-another topic already in flight" or "this may turn out to be
389
-useful"). Do not read too much into a topic being in (or not in)
390
-'seen'. The ones marked with '.' do not appear in any of the
391
-integration branches, but I am still holding onto them.
392
-
384
+topic is stable enough to be used and are candidate to be in a future
385
+release). Commits prefixed with '-' are only in 'seen', and aren't
386
+considered "accepted" at all. A topic without enough support may be
387
+discarded after a long period of no activity.
388
389
Copies of the source code to Git live in many repositories, and the
390
following is a list of the ones I push into or their mirrors. Some