I maintain this mirror, and hopefully we can make it semi-official. It
has the same refs as the GitHub one except for the GitHub "pull" refs:
$ diff -u \
<(git ls-remote https://gitlab.com/git-vcs/git.git/) \
<(git ls-remote https://github.com/git/git/|grep -v refs/pull)
$
Although I had to delete the stale "pu" manually just now.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
A new topic that is still not ready for 'pu' which uses a topic in
flight appear in the description of the latter as "used by", even
though it does not appear in the report anywhere else. Leave a note
to the place where this bug happens, as I do not have time to fix it
right now.
Just like "Will merge to 'next'" is automatically promoted to "Will
merge to 'master'" once the topic is merged to 'next', transition
two more states automatically when a topic is merged to 'next'.
"Will merge to and cook in 'next'" will become "Will cook in 'next'"
"Will merge to 'next' and then to 'master'" will become "Will merge
to 'master'".
This should not grok an arbitrary object name as "cook -w $name" is
supposed to be getting a filename, but it is handy to say "cook -w
HEAD" and get "git cat-file -p HEAD:whats-cooking.txt | cook -w -",
i.e. "which topics did I publicly threaten the list to merge soon?"
This _might_ make things easier to read, together with an extra
blank line between each topic.
Adjust Meta/Reintegrate to read and strip the extra indentation to
avoid breaking the merge log messages. "Meta/cook -w" also has
been adjusted to read and strip the extra indentation before finding
the markers for "will-do".
Earlier I used to use author date, but committer date is a better measure
of the age of the topic considering that topics in pu can be and are
sometimes amended.
