Most git:// URLs listed for the copies of the Git repository
have working corresponding https:// URLs that can be given
to a browser to browse the repository interactively. List
https:// URL instead of git:// URL for such repositories.
The former is also more secure, even though it may be more
expensive.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
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>
Even though the paragraph before this one is pretty clear that
topics are first merged to 'master' and then to 'maint', it was
misleading to say 'maint' is merged to 'master' to propagate fixes
forward, as most of the time, such an upmerge is a noop because
topics merged to 'maint' are usually merged to 'master' already.
These up-merges are done primarily to make sure that the tip of
'master' has updated release notes from all the maintenance tracks,
so be explicit about that to avoid confusion.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In addition to the usual sample revision updates, talk about the
"broken out" repo and clarify that topics can fork from commits
older than the tip of the 'master' for bugfix topics.
Now its nntp archive seems to have stopped reinjecting ancient
articles with recent article numbers, it is more usable for general
public. Advertise it over gmane (which is still operational just
fine).
Clarify what it means to be in "pu" (i.e. not much).
Also drop the list of people who help the project; keeping track of
it is a maintenance burden, especially if we want to do so fairly,
and retiring those who used to be active but no longer is tricky.
