Skip to contentSkip to conversation

This list is now also archived on lore.kernel.org/git

PATCH In review Konstantin Ryabitsev 8 participants 28 messages Nov 20, 2019 – Dec 4, 2019 Documentation

lore
Share & tools
lore
#0 lore raw

Hi, all:

I used Eric's public-inbox.org archives to set up our own copy on lore.kernel.org and identical list archives are now available on that server.

I spoke with Eric and he recommends that official project documentation starts using lore.kernel.org/git URLs in daily use and git's official documentation in order to allow him more freedom of decision when it comes to hosting his equipment. The URLs at both domains remain the same, e.g.:

- https://public-inbox.org/git/[email protected]/
- https://lore.kernel.org/git/[email protected]/

Best regards,
-K

#1 lore raw
Quoted 5 lines · Konstantin Ryabitsev

Hi, all:

I used Eric's public-inbox.org archives to set up our own copy on lore.kernel.org and identical list archives are now available on that server.

Almost :) I forget it exists, but there's the "gmane:$ARTICLE_NUM" altid mapping search support on my server for legacy gmane URLs.

Instructions to set it up:
https://public-inbox.org/meta/[email protected]/

Quoted 5 lines

I spoke with Eric and he recommends that official project documentation starts using lore.kernel.org/git URLs in daily use and git's official documentation in order to allow him more freedom of decision when it comes to hosting his equipment. The URLs at both domains remain the same, e.g.:

Yup, .org TLD renewal costs will likely go up and I won't pay higher costs to keep .org domains.

The system running public-inbox.org (and the recommended onions(*)) will stay running and will have bleeding edge code on it.

* Accessible via Tor, no need to depend on registrars:
http://hjrcffqmbrq6wope.onion/
http://ou63pmih66umazou.onion/
http://czquwvybam4bgbro.onion/

#2 lore raw
Quoted 27 lines · Eric Wong
Quoted 5 lines · Konstantin Ryabitsev

Hi, all:

I used Eric's public-inbox.org archives to set up our own copy on lore.kernel.org and identical list archives are now available on that server.

Almost :) I forget it exists, but there's the "gmane:$ARTICLE_NUM" altid mapping search support on my server for legacy gmane URLs.

Instructions to set it up:
https://public-inbox.org/meta/[email protected]/

Quoted 5 lines

I spoke with Eric and he recommends that official project documentation starts using lore.kernel.org/git URLs in daily use and git's official documentation in order to allow him more freedom of decision when it comes to hosting his equipment. The URLs at both domains remain the same, e.g.:

Yup, .org TLD renewal costs will likely go up and I won't pay higher costs to keep .org domains.

The system running public-inbox.org (and the recommended onions(*)) will stay running and will have bleeding edge code on it.

Quoted 4 lines

* Accessible via Tor, no need to depend on registrars:
http://hjrcffqmbrq6wope.onion/
http://ou63pmih66umazou.onion/
http://czquwvybam4bgbro.onion/

I think it would make sense for the Git SFC arm of things[1] to consider taking over the public-inbox.org domain rather than letting it expire (of course contingent on your approval) and turning it into a CNAME (or other redirect) for lore.kernel.org.

We have a lot of mailing list and some (~130 commits) git.git commit references to that domain. It seems like a worthwhile expense to me to pay for the renewal of it rather than having it turn into e.g. some spam landing page as the registration expires.

1. Disclaimer: I'm one of the people who'd vote on making that decision if it came to that, but this E-Mail is, as they say, just like, my opinion, man :)

#3 lore raw
Quoted 5 lines · Ævar Arnfjörð Bjarmason

I think it would make sense for the Git SFC arm of things[1] to consider taking over the public-inbox.org domain rather than letting it expire (of course contingent on your approval) and turning it into a CNAME (or other redirect) for lore.kernel.org.

Quoted 8 lines

We have a lot of mailing list and some (~130 commits) git.git commit references to that domain. It seems like a worthwhile expense to me to pay for the renewal of it rather than having it turn into e.g. some spam landing page as the registration expires.

1. Disclaimer: I'm one of the people who'd vote on making that decision if it came to that, but this E-Mail is, as they say, just like, my opinion, man :)

I'm also one of those people, and I'd consider it as well. A lot of it would depend on the cost, and what happens with this whole .org registrar thing.

-Peff

#4 lore raw
In reply to Ævar Arnfjörð Bjarmason
Quoted 14 lines · Ævar Arnfjörð Bjarmason
Quoted 8 lines · Eric Wong

Yup, .org TLD renewal costs will likely go up and I won't pay higher costs to keep .org domains.

The system running public-inbox.org (and the recommended onions(*)) will stay running and will have bleeding edge code on it.

Quoted 4 lines

* Accessible via Tor, no need to depend on registrars:
http://hjrcffqmbrq6wope.onion/
http://ou63pmih66umazou.onion/
http://czquwvybam4bgbro.onion/

Quoted 4 lines

I think it would make sense for the Git SFC arm of things[1] to consider taking over the public-inbox.org domain rather than letting it expire (of course contingent on your approval) and turning it into a CNAME (or other redirect) for lore.kernel.org.

There's also https://public-inbox.org/meta/ and other (FLOSS-related) mirrors and the root landing page itself.

Quoted 4 lines

We have a lot of mailing list and some (~130 commits) git.git commit references to that domain. It seems like a worthwhile expense to me to pay for the renewal of it rather than having it turn into e.g. some spam landing page as the registration expires.

One feature I'd like to see in public-inbox and even git porcelain and web viewers is the ability to rewrite URLs on the client-side, similar to .mailmap. It would make sense they all share the same configuration.

Quoted 3 lines

1. Disclaimer: I'm one of the people who'd vote on making that decision if it came to that, but this E-Mail is, as they say, just like, my opinion, man :)

Fwiw, I intentionally keep the branding of the public-inbox project weak (no trademarks, logos, real homepage) because I believe strong branding and consolidation of influence/identity leads to centralization. It's easier to fork projects when there's no logos, trademarks or other branding to deal with.

I also believe the term "public inbox" is a much more powerful idea than any project could be. To that end, I'm happy SourceHut (and maybe others) also use that term. The "public-inbox" project is just one cheapskate's anti-consumerist interpretation of that idea :>

I pretty much say whatever I can to sabotage my own credibility as a result. I'm also shy and introverted, so branding and good marketing does not compute :P

#5 lore raw
In reply to Konstantin Ryabitsev
Quoted 4 lines · Konstantin Ryabitsev

I used Eric's public-inbox.org archives to set up our own copy on lore.kernel.org and identical list archives are now available on that server.

Quoted 8 lines

I spoke with Eric and he recommends that official project documentation starts using lore.kernel.org/git URLs in daily use and git's official documentation in order to allow him more freedom of decision when it comes to hosting his equipment. The URLs at both domains remain the same, e.g.:

- https://public-inbox.org/git/[email protected]/
- https://lore.kernel.org/git/[email protected]/

Thank you for setting this up (and thank you Eric for the public-inbox code and service; it's _so_ much nicer than the previous alternatives).

It sounds like we should do something like the series below.

[1/2]: doc: recommend lore.kernel.org over public-inbox.org [2/2]: doc: replace public-inbox links with lore.kernel.org

 Documentation/MyFirstContribution.txt              |  2 +-
 Documentation/git-bisect-lk2009.txt                |  2 +-
 Documentation/git.txt                              |  2 +-
 Documentation/technical/commit-graph.txt           | 10 +++++-----
 .../technical/hash-function-transition.txt         | 14 +++++++-------
 Documentation/technical/multi-pack-index.txt       |  4 ++--
 Documentation/technical/partial-clone.txt          | 12 ++++++------
 README.md                                          |  2 +-
 apply.c                                            |  2 +-
 sha1dc/sha1.c                                      |  2 +-
 t/t0021-conversion.sh                              |  4 ++--
 t/t4038-diff-combined.sh                           |  2 +-
 tree-walk.c                                        |  2 +-
 13 files changed, 30 insertions(+), 30 deletions(-)

-Peff

#6 lore raw

PATCH 1/2 doc: recommend lore.kernel.org over public-inbox.org

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
or if you like:
https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

---
And it's one character shorter. Think of all of the bytes saved!

 Documentation/MyFirstContribution.txt | 2 +-
 Documentation/git.txt                 | 2 +-
 README.md                             | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
Documentation/MyFirstContribution.txt +1 -1
index 5e9b808f5f..5922803d87 100644
@@ -970,7 +970,7 @@ reviewers the changes you've made that may not be as visible.
 You will also need to go and find the Message-Id of your previous cover letter.
 You can either note it when you send the first series, from the output of `git
 send-email`, or you can look it up on the
-https://public-inbox.org/git[mailing list]. Find your cover letter in the
+https://lore.kernel.org/git[mailing list]. Find your cover letter in the
 archives, click on it, then click "permalink" or "raw" to reveal the Message-Id
 header. It should match:
 
Documentation/git.txt +1 -1
index 9b82564d1a..5f5b85ba27 100644
@@ -928,7 +928,7 @@ Reporting Bugs
 Report bugs to the Git mailing list <[email protected]> where the
 development and maintenance is primarily done.  You do not have to be
 subscribed to the list to send a message there.  See the list archive
-at https://public-inbox.org/git for previous bug reports and other
+at https://lore.kernel.org/git for previous bug reports and other
 discussions.
 
 Issues which are security relevant should be disclosed privately to
README.md +1 -1
index e1d2b82209..9d4564c8aa 100644
@@ -35,7 +35,7 @@ requests, comments and patches to [email protected] (read
 [Documentation/SubmittingPatches][] for instructions on patch submission).
 To subscribe to the list, send an email with just "subscribe git" in
 the body to [email protected]. The mailing list archives are
-available at <https://public-inbox.org/git/>,
+available at <https://lore.kernel.org/git/>,
 <http://marc.info/?l=git> and other archival sites.
 
 Issues which are security relevant should be disclosed privately to
Signature · 1 line
2.24.0.778.ge5f6c7a838
Acked-by on v1 1/2
#7 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Quoted 11 lines · Jeff King

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
or if you like:
https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

---
And it's one character shorter. Think of all of the bytes saved!

:> URL length has always bothered me. peff.net/git/$MESSAGE_ID/ would be nice to have, as well :)

Anyways, consider this series:

(and I doubt I'll keep paying for 80x24.org, either...)

#8 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Hi,

Quoted 8 lines · Eric Wong
Quoted 7 lines · Jeff King

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
or if you like:
https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

One of the things I appreciate most about https://public-inbox.org/git is that you can clone it. I just tried this with
https://lore.kernel.org/git/...

$ git clone https://lore.kernel.org/git/  lore-git
Cloning into 'lore-git'...
warning: You appear to have cloned an empty repository.

Is this something other people also care about?

Ciao,
Dscho

Quoted 14 lines
Quoted 4 lines

---
And it's one character shorter. Think of all of the bytes saved!

:> URL length has always bothered me. peff.net/git/$MESSAGE_ID/ would be nice to have, as well :)

Anyways, consider this series:

(and I doubt I'll keep paying for 80x24.org, either...)

#9 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Quoted 10 lines · Johannes Schindelin
Quoted 8 lines · Eric Wong
Quoted 7 lines · Jeff King

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
or if you like:
https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

Quoted 7 lines

One of the things I appreciate most about https://public-inbox.org/git is that you can clone it. I just tried this with
https://lore.kernel.org/git/...

$ git clone https://lore.kernel.org/git/  lore-git
Cloning into 'lore-git'...
warning: You appear to have cloned an empty repository.

Oops, that's a usability issue I hope to fix at some point.

Quoted 1 line

Is this something other people also care about?

Instructions are actually at the bottom:

   git clone --mirror https://lore.kernel.org/git/0 git/git/0.git

The "0" is the "epoch", and larger repos have multiple epochs, roughly 1GB each. https://lore.kernel.org/lkml/ has 0..7, right now.

#10 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Hi,

Quoted 15 lines · Eric Wong
Quoted 14 lines · Johannes Schindelin
Quoted 8 lines · Eric Wong
Quoted 7 lines · Jeff King

Since lore.kernel.org now has the same archive as public-inbox.org and may have more longevity going forward[1], let's recommend people use it for finding or referencing messages.

[1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
or if you like:
https://lore.kernel.org/git/20191120195556.GA25189@dcvr/

One of the things I appreciate most about https://public-inbox.org/git is that you can clone it. I just tried this with
https://lore.kernel.org/git/...

Quoted 5 lines
Quoted 3 lines
$ git clone https://lore.kernel.org/git/  lore-git
Cloning into 'lore-git'...
warning: You appear to have cloned an empty repository.

Oops, that's a usability issue I hope to fix at some point.

That would be nice. As you can tell from my puzzlement, not everybody scrolls down to the instruction (which I finally found after your comment)...

:-D

Quoted 8 lines
Quoted 1 line

Is this something other people also care about?

Instructions are actually at the bottom:

   git clone --mirror https://lore.kernel.org/git/0 git/git/0.git

The "0" is the "epoch", and larger repos have multiple epochs, roughly 1GB each. https://lore.kernel.org/lkml/ has 0..7, right now.

Okay, so how does that work, is the idea that you should graft them together using replacement objects if you want to have the full archive?

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

Thanks,
Dscho

#11 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Quoted 6 lines · Johannes Schindelin
Quoted 2 lines · Eric Wong

The "0" is the "epoch", and larger repos have multiple epochs, roughly 1GB each. https://lore.kernel.org/lkml/ has 0..7, right now.

Okay, so how does that work, is the idea that you should graft them together using replacement objects if you want to have the full archive?

Yes. Except we don't actually use grafts/replace and users can currently only clone the latest epoch of LKML. In the future, it should also be easy to jettison old epochs if space is limited.

Quoted 2 lines

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz

grokmirror could be a bit of a pain to install because of Python dependencies, so periodically attempting to clone the next numbered epoch ought to be fine, too.

I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"

#12 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Hi Eric,

Quoted 8 lines · Eric Wong
Quoted 2 lines · Johannes Schindelin

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz

Quoted 7 lines

grokmirror could be a bit of a pain to install because of Python dependencies, so periodically attempting to clone the next numbered epoch ought to be fine, too.

I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"

I just had a look at its contents:

-- snip --
; example public-inbox config snippet for "git"
; see public-inbox-config(5) manpage for more details:
; https://public-inbox.org/public-inbox-config.html
[publicinbox "git"]
inboxdir = /path/to/top-level-inbox
; note: public-inbox before v1.2.0 used "mainrepo" ; instead of "inboxdir", both remain supported after 1.2 mainrepo = /path/to/top-level-inbox
address = [email protected]
listid = git.vger.kernel.org
filter = PublicInbox::Filter::Mirror
newsgroup = org.kernel.vger.git
nntpmirror = nntp://nntp.lore.kernel.org/org.kernel.vger.git
-- snap --

Isn't inboxdir and mainrepo incorrect?

And yes, adding epoch information there would be very welcome.

Thanks,
Dscho

#13 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Quoted 38 lines · Johannes Schindelin

Hi Eric,

Quoted 8 lines · Eric Wong
Quoted 2 lines · Johannes Schindelin

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz

Quoted 7 lines

grokmirror could be a bit of a pain to install because of Python dependencies, so periodically attempting to clone the next numbered epoch ought to be fine, too.

I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"

I just had a look at its contents:

-- snip --
; example public-inbox config snippet for "git"
; see public-inbox-config(5) manpage for more details:
; https://public-inbox.org/public-inbox-config.html
[publicinbox "git"]
inboxdir = /path/to/top-level-inbox
; note: public-inbox before v1.2.0 used "mainrepo" ; instead of "inboxdir", both remain supported after 1.2 mainrepo = /path/to/top-level-inbox
address = [email protected]
listid = git.vger.kernel.org
filter = PublicInbox::Filter::Mirror
newsgroup = org.kernel.vger.git
nntpmirror = nntp://nntp.lore.kernel.org/org.kernel.vger.git
-- snap --

Quoted 1 line

Isn't inboxdir and mainrepo incorrect?

How so? It's fine to have both in case users need to downgrade to older versions of public-inbox.

Quoted 1 line

And yes, adding epoch information there would be very welcome.

Noted. Not sure if the "modified" and "fingerprint" keys of manifest would make sense there, too...

#14 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Hi Eric,

Quoted 39 lines · Eric Wong
Quoted 38 lines · Johannes Schindelin

Hi Eric,

Quoted 8 lines · Eric Wong
Quoted 2 lines · Johannes Schindelin

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz

Quoted 7 lines

grokmirror could be a bit of a pain to install because of Python dependencies, so periodically attempting to clone the next numbered epoch ought to be fine, too.

I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"

I just had a look at its contents:

-- snip --
; example public-inbox config snippet for "git"
; see public-inbox-config(5) manpage for more details:
; https://public-inbox.org/public-inbox-config.html
[publicinbox "git"]
inboxdir = /path/to/top-level-inbox
; note: public-inbox before v1.2.0 used "mainrepo" ; instead of "inboxdir", both remain supported after 1.2 mainrepo = /path/to/top-level-inbox
address = [email protected]
listid = git.vger.kernel.org
filter = PublicInbox::Filter::Mirror
newsgroup = org.kernel.vger.git
nntpmirror = nntp://nntp.lore.kernel.org/org.kernel.vger.git
-- snap --

Quoted 4 lines
Quoted 1 line

Isn't inboxdir and mainrepo incorrect?

How so? It's fine to have both in case users need to downgrade to older versions of public-inbox.

I must have misinterpreted the purpose of this URL, then. I thought that was the configuration of _this_ instance, and that I could use the path indicated by mainrepo to replace the /_/text/config/raw part of the URL to get to the repo URL.

Is this just a template file, then?

Quoted 4 lines
Quoted 1 line

And yes, adding epoch information there would be very welcome.

Noted. Not sure if the "modified" and "fingerprint" keys of manifest would make sense there, too...

I have no idea what purpose they serve, so I have no opinion on this question.

Thanks,
Dscho

#15 lore raw

Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org

Quoted 48 lines · Johannes Schindelin

Hi Eric,

Quoted 39 lines · Eric Wong
Quoted 38 lines · Johannes Schindelin

Hi Eric,

Quoted 8 lines · Eric Wong
Quoted 2 lines · Johannes Schindelin

And: if I want to track the latest mails in GitGitGadget, what indication will I have that I'll need to switch to .../1?

You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz

Quoted 7 lines

grokmirror could be a bit of a pain to install because of Python dependencies, so periodically attempting to clone the next numbered epoch ought to be fine, too.

I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"

I just had a look at its contents:

-- snip --
; example public-inbox config snippet for "git"
; see public-inbox-config(5) manpage for more details:
; https://public-inbox.org/public-inbox-config.html
[publicinbox "git"]
inboxdir = /path/to/top-level-inbox
; note: public-inbox before v1.2.0 used "mainrepo" ; instead of "inboxdir", both remain supported after 1.2 mainrepo = /path/to/top-level-inbox
address = [email protected]
listid = git.vger.kernel.org
filter = PublicInbox::Filter::Mirror
newsgroup = org.kernel.vger.git
nntpmirror = nntp://nntp.lore.kernel.org/org.kernel.vger.git
-- snap --

Quoted 4 lines
Quoted 1 line

Isn't inboxdir and mainrepo incorrect?

How so? It's fine to have both in case users need to downgrade to older versions of public-inbox.

Quoted 6 lines

I must have misinterpreted the purpose of this URL, then. I thought that was the configuration of _this_ instance, and that I could use the path indicated by mainrepo to replace the /_/text/config/raw part of the URL to get to the repo URL.

Is this just a template file, then?

It's a config snippet that can be copy+pasted into ~/.public-inbox/config and edited to suit the local machine (but also human-readable and git-config(1)-parseable)

Both "mainrepo" and "inboxdir" refer to local paths, not URLs, currently. But it would be nice to access inboxes over WebDAV or similar :>

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

And yes, adding epoch information there would be very welcome.

Noted. Not sure if the "modified" and "fingerprint" keys of manifest would make sense there, too...

I have no idea what purpose they serve, so I have no opinion on this question.

They're timestamps and checksums used to reduce the cost of checking multiple repos for updates. It's hugely beneficial when there's 100s or 1000s of repos to mirror. grokmirror only makes one HTTP request to get manifest.js.gz, and only runs fetches for ones that need updating.

It's a less useful for git@vger since there's only one epoch, currently; and checking for the existence of a next one (1.git) isn't that expensive.

#16 lore raw

PATCH 2/2 doc: replace public-inbox links with lore.kernel.org

In reply to Jeff King

Since we're now recommending lore.kernel.org (and because the public-inbox.org domain might eventually go away), let's update our internal references to use it, too. That future-proofs our references, and sets the example we want people to follow.

---
 Documentation/git-bisect-lk2009.txt                |  2 +-
 Documentation/technical/commit-graph.txt           | 10 +++++-----
 .../technical/hash-function-transition.txt         | 14 +++++++-------
 Documentation/technical/multi-pack-index.txt       |  4 ++--
 Documentation/technical/partial-clone.txt          | 12 ++++++------
 apply.c                                            |  2 +-
 sha1dc/sha1.c                                      |  2 +-
 t/t0021-conversion.sh                              |  4 ++--
 t/t4038-diff-combined.sh                           |  2 +-
 tree-walk.c                                        |  2 +-
 10 files changed, 27 insertions(+), 27 deletions(-)
Documentation/git-bisect-lk2009.txt +1 -1
index e99925184d..5bcf4d9b94 100644
@@ -1350,7 +1350,7 @@ References
 - [[[1]]] https://www.nist.gov/sites/default/files/documents/director/planning/report02-3.pdf['The Economic Impacts of Inadequate Infratructure for Software Testing'.  Nist Planning Report 02-3], see Executive Summary and Chapter 8.
 - [[[2]]] http://www.oracle.com/technetwork/java/codeconvtoc-136057.html['Code Conventions for the Java Programming Language'. Sun Microsystems.]
 - [[[3]]] https://en.wikipedia.org/wiki/Software_maintenance['Software maintenance'. Wikipedia.]
-- [[[4]]] https://public-inbox.org/git/[email protected]/[Junio C Hamano. 'Automated bisect success story'.]
+- [[[4]]] https://lore.kernel.org/git/[email protected]/[Junio C Hamano. 'Automated bisect success story'.]
 - [[[5]]] https://lwn.net/Articles/317154/[Christian Couder. 'Fully automated bisecting with "git bisect run"'. LWN.net.]
 - [[[6]]] https://lwn.net/Articles/277872/[Jonathan Corbet. 'Bisection divides users and developers'. LWN.net.]
 - [[[7]]] http://marc.info/?l=linux-kernel&m=119702753411680&w=2[Ingo Molnar. 'Re: BUG 2.6.23-rc3 can't see sd partitions on Alpha'. Linux-kernel mailing list.]
Documentation/technical/commit-graph.txt +5 -5
index 729fbcb32f..25eabe36cf 100644
@@ -323,14 +323,14 @@ Related Links
 [0] https://bugs.chromium.org/p/git/issues/detail?id=8
     Chromium work item for: Serialized Commit Graph
 
-[1] https://public-inbox.org/git/[email protected]/
+[1] https://lore.kernel.org/git/[email protected]/
     An abandoned patch that introduced generation numbers.
 
-[2] https://public-inbox.org/git/[email protected]/
+[2] https://lore.kernel.org/git/[email protected]/
     Discussion about generation numbers on commits and how they interact
     with fsck.
 
-[3] https://public-inbox.org/git/[email protected]/
+[3] https://lore.kernel.org/git/[email protected]/
     More discussion about generation numbers and not storing them inside
     commit objects. A valuable quote:
 
@@ -342,9 +342,9 @@ Related Links
      commit objects (i.e., packv4 or something like the "metapacks" I
      proposed a few years ago)."
 
-[4] https://public-inbox.org/git/[email protected]/T/#u
+[4] https://lore.kernel.org/git/[email protected]/T/#u
     A patch to remove the ahead-behind calculation from 'status'.
 
-[5] https://public-inbox.org/git/[email protected]/
+[5] https://lore.kernel.org/git/[email protected]/
     A discussion of a "two-dimensional graph position" that can allow reading
     multiple commit-graph chains at the same time.
Documentation/technical/hash-function-transition.txt +7 -7
index 2ae8fa470a..4744a3f6c6 100644
@@ -730,7 +730,7 @@ adoption.
 
 Using hash functions in parallel
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-(e.g. https://public-inbox.org/git/[email protected]/ )
+(e.g. https://lore.kernel.org/git/[email protected]/ )
 Objects newly created would be addressed by the new hash, but inside
 such an object (e.g. commit) it is still possible to address objects
 using the old hash function.
@@ -783,7 +783,7 @@ [email protected], [email protected], [email protected],
 [email protected]
 
 Initial version sent to
-http://public-inbox.org/git/[email protected]
+http://lore.kernel.org/git/[email protected]
 
 2017-03-03 [email protected]
 Incorporated suggestions from jonathantanmy and sbeller:
@@ -820,8 +820,8 @@ Later history:
  edits. This document history is no longer being maintained as it
  would now be superfluous to the commit log
 
-[1] http://public-inbox.org/git/CA+55aFzJtejiCjV0e43+9oR3QuJK2PiFiLQemytoLpyJWe6P9w@mail.gmail.com/
-[2] http://public-inbox.org/git/CA+55aFz+gkAsDZ24zmePQuEs1XPS9BP_s8O7Q4wQ7LV7X5-oDA@mail.gmail.com/
-[3] http://public-inbox.org/git/[email protected]/
-[4] http://public-inbox.org/git/[email protected]
-[5] https://public-inbox.org/git/CAJo=hJtoX9=AyLHHpUJS7fueV9ciZ_MNpnEPHUz8Whui6g9F0A@mail.gmail.com/
+[1] http://lore.kernel.org/git/CA+55aFzJtejiCjV0e43+9oR3QuJK2PiFiLQemytoLpyJWe6P9w@mail.gmail.com/
+[2] http://lore.kernel.org/git/CA+55aFz+gkAsDZ24zmePQuEs1XPS9BP_s8O7Q4wQ7LV7X5-oDA@mail.gmail.com/
+[3] http://lore.kernel.org/git/[email protected]/
+[4] http://lore.kernel.org/git/[email protected]
+[5] https://lore.kernel.org/git/CAJo=hJtoX9=AyLHHpUJS7fueV9ciZ_MNpnEPHUz8Whui6g9F0A@mail.gmail.com/
Documentation/technical/multi-pack-index.txt +2 -2
index d7e57639f7..1e31239696 100644
@@ -102,8 +102,8 @@ Related Links
 [0] https://bugs.chromium.org/p/git/issues/detail?id=6
     Chromium work item for: Multi-Pack Index (MIDX)
 
-[1] https://public-inbox.org/git/[email protected]/
+[1] https://lore.kernel.org/git/[email protected]/
     An earlier RFC for the multi-pack-index feature
 
-[2] https://public-inbox.org/git/alpine.DEB.2.20.1803091557510.23109@alexmv-linux/
+[2] https://lore.kernel.org/git/alpine.DEB.2.20.1803091557510.23109@alexmv-linux/
     Git Merge 2018 Contributor's summit notes (includes discussion of MIDX)
Documentation/technical/partial-clone.txt +6 -6
index 210373e258..3bd3a4d45d 100644
@@ -350,26 +350,26 @@ Related Links
 [0] https://crbug.com/git/2
     Bug#2: Partial Clone
 
-[1] https://public-inbox.org/git/[email protected]/ +
+[1] https://lore.kernel.org/git/[email protected]/ +
     Subject: [RFC] Add support for downloading blobs on demand +
     Date: Fri, 13 Jan 2017 10:52:53 -0500
 
-[2] https://public-inbox.org/git/[email protected]/ +
+[2] https://lore.kernel.org/git/[email protected]/ +
     Subject: [PATCH 00/18] Partial clone (from clone to lazy fetch in 18 patches) +
     Date: Fri, 29 Sep 2017 13:11:36 -0700
 
-[3] https://public-inbox.org/git/[email protected]/ +
+[3] https://lore.kernel.org/git/[email protected]/ +
     Subject: Proposal for missing blob support in Git repos +
     Date: Wed, 26 Apr 2017 15:13:46 -0700
 
-[4] https://public-inbox.org/git/[email protected]/ +
+[4] https://lore.kernel.org/git/[email protected]/ +
     Subject: [PATCH 00/10] RFC Partial Clone and Fetch +
     Date: Wed,  8 Mar 2017 18:50:29 +0000
 
-[5] https://public-inbox.org/git/[email protected]/ +
+[5] https://lore.kernel.org/git/[email protected]/ +
     Subject: [PATCH v7 00/10] refactor the filter process code into a reusable module +
     Date: Fri,  5 May 2017 11:27:52 -0400
 
-[6] https://public-inbox.org/git/[email protected]/ +
+[6] https://lore.kernel.org/git/[email protected]/ +
     Subject: [RFC/PATCH v2 0/1] Add support for downloading blobs on demand +
     Date: Fri, 14 Jul 2017 09:26:50 -0400
apply.c +1 -1
index b9291f5f7b..a2f0f804fe 100644
@@ -450,7 +450,7 @@ static char *find_name_gnu(struct strbuf *root,
 
 	/*
 	 * Proposed "new-style" GNU patch/diff format; see
-	 * https://public-inbox.org/git/[email protected]/
+	 * https://lore.kernel.org/git/[email protected]/
 	 */
 	if (unquote_c_style(&name, line, NULL)) {
 		strbuf_release(&name);
sha1dc/sha1.c +1 -1
index 9d3cf81d4d..4afc989a9e 100644
@@ -98,7 +98,7 @@
 /*
  * Defines Big Endian on a whitelist of OSs that are known to be Big
  * Endian-only. See
- * https://public-inbox.org/git/[email protected]/
+ * https://lore.kernel.org/git/[email protected]/
  */
 #define SHA1DC_BIGENDIAN
 
t/t0021-conversion.sh +2 -2
index c954c709ad..6c6d77b51a 100755
@@ -35,7 +35,7 @@ filter_git () {
 # Compare two files and ensure that `clean` and `smudge` respectively are
 # called at least once if specified in the `expect` file. The actual
 # invocation count is not relevant because their number can vary.
-# c.f. http://public-inbox.org/git/[email protected]/
+# c.f. http://lore.kernel.org/git/[email protected]/
 test_cmp_count () {
 	expect=$1
 	actual=$2
@@ -50,7 +50,7 @@ test_cmp_count () {
 
 # Compare two files but exclude all `clean` invocations because Git can
 # call `clean` zero or more times.
-# c.f. http://public-inbox.org/git/[email protected]/
+# c.f. http://lore.kernel.org/git/[email protected]/
 test_cmp_exclude_clean () {
 	expect=$1
 	actual=$2
t/t4038-diff-combined.sh +1 -1
index b5a56895e8..94680836ce 100755
@@ -354,7 +354,7 @@ test_expect_failure 'combine diff coalesce three parents' '
 '
 
 # Test for a bug reported at
-# https://public-inbox.org/git/[email protected]/
+# https://lore.kernel.org/git/[email protected]/
 # where a delete lines were missing from combined diff output when they
 # occurred exactly before the context lines of a later change.
 test_expect_success 'combine diff missing delete bug' '
tree-walk.c +1 -1
index bea819d826..d5a8e096a6 100644
@@ -1124,7 +1124,7 @@ static enum interesting do_match(struct index_state *istate,
 		 * later on.
 		 * max_depth is ignored but we may consider support it
 		 * in future, see
-		 * https://public-inbox.org/git/[email protected]/
+		 * https://lore.kernel.org/git/[email protected]/
 		 */
 		if (ps->recursive && S_ISDIR(entry->mode))
 			return entry_interesting;
Signature · 1 line
2.24.0.778.ge5f6c7a838
#17 lore raw

Re: [PATCH 2/2] doc: replace public-inbox links with lore.kernel.org

Quoted 4 lines · Jeff King

Since we're now recommending lore.kernel.org (and because the public-inbox.org domain might eventually go away), let's update our internal references to use it, too. That future-proofs our references, and sets the example we want people to follow.

This is a great idea. I clicked a few of the links to verify they work.

-Stolee

#18 lore raw

cover Hi Peff,

In reply to Jeff King

Thanks for doing this. Perhaps while we're at it, we want to change all of the MARC and Gmane links as well? The series below does this.

I've based my series on top of yours so if you need to do a reroll, feel free to pick my changes in.

Denton Liu (2):
doc: replace MARC links with LKML
RelNotes: replace Gmane with real Message-IDs

 Documentation/RelNotes/1.6.2.txt    | 2 +-
 Documentation/RelNotes/1.6.3.txt    | 2 +-
 Documentation/RelNotes/1.6.4.txt    | 2 +-
 Documentation/RelNotes/1.6.5.txt    | 2 +-
 Documentation/RelNotes/1.6.6.txt    | 2 +-
 Documentation/RelNotes/1.8.4.txt    | 2 +-
 Documentation/RelNotes/2.5.0.txt    | 3 ++-
 Documentation/RelNotes/2.8.3.txt    | 4 ++--
 Documentation/RelNotes/2.9.0.txt    | 2 +-
 Documentation/git-bisect-lk2009.txt | 2 +-
 Documentation/gitcli.txt            | 4 ++--
 Documentation/user-manual.txt       | 4 ++--
 t/t6021-merge-criss-cross.sh        | 2 +-
 13 files changed, 17 insertions(+), 16 deletions(-)
Signature · 1 line
2.24.0.504.g3cd56eb17d
#19 lore raw

PATCH 1/2 doc: replace MARC links with LKML

Since we're now recommending lore.kernel.org, replace marc.info links with lore.kernel.org.

Although MARC has been around for a long time, nothing lasts forever (see Gmane). Since MARC uses opaque message identifiers, switching to LKML should be a strict improvement since, even if LKML goes down, the Message-ID will allow future readers to look up the referenced messages on any other archive.

We leave behind one reference to MARC in the README.md since it's a perfectly fine mail archive for personal reading, just not for linking messages for the future.

---
 Documentation/git-bisect-lk2009.txt | 2 +-
 Documentation/gitcli.txt            | 4 ++--
 Documentation/user-manual.txt       | 4 ++--
 t/t6021-merge-criss-cross.sh        | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)
Documentation/git-bisect-lk2009.txt +1 -1
index 5bcf4d9b94..72dbe6dbea 100644
@@ -1353,6 +1353,6 @@ References
 - [[[4]]] https://lore.kernel.org/git/[email protected]/[Junio C Hamano. 'Automated bisect success story'.]
 - [[[5]]] https://lwn.net/Articles/317154/[Christian Couder. 'Fully automated bisecting with "git bisect run"'. LWN.net.]
 - [[[6]]] https://lwn.net/Articles/277872/[Jonathan Corbet. 'Bisection divides users and developers'. LWN.net.]
-- [[[7]]] http://marc.info/?l=linux-kernel&m=119702753411680&w=2[Ingo Molnar. 'Re: BUG 2.6.23-rc3 can't see sd partitions on Alpha'. Linux-kernel mailing list.]
+- [[[7]]] https://lore.kernel.org/lkml/[email protected]/[Ingo Molnar. 'Re: BUG 2.6.23-rc3 can't see sd partitions on Alpha'. Linux-kernel mailing list.]
 - [[[8]]] https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html[Junio C Hamano and the git-list. 'git-bisect(1) Manual Page'. Linux Kernel Archives.]
 - [[[9]]] https://github.com/Ealdwulf/bbchop[Ealdwulf. 'bbchop'. GitHub.]
Documentation/gitcli.txt +2 -2
index 4b32876b6e..373cfa2264 100644
@@ -211,8 +211,8 @@ only affects the files in the working tree, but with
 entries, and with `--cached`, it modifies only the index
 entries.
 
-See also http://marc.info/?l=git&m=116563135620359 and
-http://marc.info/?l=git&m=119150393620273 for further
+See also https://lore.kernel.org/git/[email protected]/ and
+https://lore.kernel.org/git/[email protected]/ for further
 information.
 
 Some other commands that also work on files in the working tree and/or
Documentation/user-manual.txt +2 -2
index 06bd8994ee..833652983f 100644
@@ -4574,5 +4574,5 @@ Write a chapter on using plumbing and writing scripts.
 Alternates, clone -reference, etc.
 
 More on recovery from repository corruption.  See:
-	http://marc.info/?l=git&m=117263864820799&w=2
-	http://marc.info/?l=git&m=117147855503798&w=2
+	https://lore.kernel.org/git/[email protected]/
+	https://lore.kernel.org/git/[email protected]/
t/t6021-merge-criss-cross.sh +1 -1
index 213deecab1..d254e020b6 100755
@@ -3,7 +3,7 @@
 # Copyright (c) 2005 Fredrik Kuivinen
 #
 
-# See http://marc.info/?l=git&m=111463358500362&w=2 for a
+# See https://lore.kernel.org/git/[email protected]/ for a
 # nice description of what this is about.
 
 
Signature · 1 line
2.24.0.504.g3cd56eb17d
#20 lore raw

PATCH 2/2 RelNotes: replace Gmane with real Message-IDs

In reply to Denton Liu

The only references to Gmane that remain are in RelNotes. Although these are definitely not in active use, they might be of historical interest for future readers so let's ensure that mail references are more robust.

Replace links to Gmane with links to LKML (which is our new preferred mailing list archive and has the Message-ID in the URL) and bare Gmane ID references with Message-IDs.

The Message-IDs were found by searching for "gmane:<id>" on
https://public-inbox.org/git/ and taking the resulting message.

---
 Documentation/RelNotes/1.6.2.txt | 2 +-
 Documentation/RelNotes/1.6.3.txt | 2 +-
 Documentation/RelNotes/1.6.4.txt | 2 +-
 Documentation/RelNotes/1.6.5.txt | 2 +-
 Documentation/RelNotes/1.6.6.txt | 2 +-
 Documentation/RelNotes/1.8.4.txt | 2 +-
 Documentation/RelNotes/2.5.0.txt | 3 ++-
 Documentation/RelNotes/2.8.3.txt | 4 ++--
 Documentation/RelNotes/2.9.0.txt | 2 +-
 9 files changed, 11 insertions(+), 10 deletions(-)
Documentation/RelNotes/1.6.2.txt +1 -1
index ad060f4f89..980adfb315 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.3.txt +1 -1
index 418c685cf8..4bcff945e0 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.4.txt +1 -1
index 7a904419f7..a2a34b43a7 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.5.txt +1 -1
index ee141c19ad..6c7f7da7eb 100644
@@ -22,7 +22,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.6.txt +1 -1
index c50b59c495..3ed1e01433 100644
@@ -64,7 +64,7 @@ users will fare this time.
    Please refer to:
 
    http://git.or.cz/gitwiki/GitFaq#non-bare
-   http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+   https://lore.kernel.org/git/[email protected]/
 
    for more details on the reason why this change is needed and the
    transition process that already took place so far.
Documentation/RelNotes/1.8.4.txt +1 -1
index 02f681b710..255e185af6 100644
@@ -58,7 +58,7 @@ Foreign interfaces, subsystems and ports.
    credential helper interface from Git.pm.
 
  * Update build for Cygwin 1.[57].  Torsten Bögershausen reports that
-   this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
+   this is fine with Cygwin 1.7 (cf. <[email protected]>) so let's try moving it
    ahead.
 
  * The credential helper to talk to keychain on OS X (in contrib/) has
Documentation/RelNotes/2.5.0.txt +2 -1
index 87044504c5..84723f912a 100644
@@ -172,7 +172,8 @@ Performance, Internal Implementation, Development Support etc.
    incorrect patch text to "git apply".  Add tests to demonstrate
    this.
 
-   I have a slight suspicion that this may be $gmane/87202 coming back
+   I have a slight suspicion that this may be
+   cf. <[email protected]> coming back
    and biting us (I seem to have said "let's run with this and see
    what happens" back then).
 
Documentation/RelNotes/2.8.3.txt +2 -2
index fedd9968e5..266c4781a8 100644
@@ -55,8 +55,8 @@ Fixes since v2.8.2
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
-   and http://thread.gmane.org/gmane.comp.version-control.git/275680.
+   See https://lkml.org/git/[email protected]/
+   and https://lkml.org/git/[email protected]/.
 
  * "git replace -e" did not honour "core.editor" configuration.
 
Documentation/RelNotes/2.9.0.txt +1 -1
index b61d36712f..d5f95b6641 100644
@@ -368,7 +368,7 @@ notes for details).
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
+   See https://lkml.org/git/[email protected]/
 
  * "merge-octopus" strategy did not ensure that the index is clean
    when merge begins.
Signature · 1 line
2.24.0.504.g3cd56eb17d
#21 lore raw

Re: [PATCH 2/2] RelNotes: replace Gmane with real Message-IDs

Quoted 5 lines · Denton Liu

The only references to Gmane that remain are in RelNotes. Although these are definitely not in active use, they might be of historical interest for future readers so let's ensure that mail references are more robust.

Replace links to Gmane with links to LKML (which is our new preferred

In this and the last patch, I had a brainfart and I thought LKML and lore.kernel.org were the same thing but obviously they're not.

Quoted 116 lines

mailing list archive and has the Message-ID in the URL) and bare Gmane ID references with Message-IDs.

The Message-IDs were found by searching for "gmane:<id>" on
https://public-inbox.org/git/ and taking the resulting message.

---
 Documentation/RelNotes/1.6.2.txt | 2 +-
 Documentation/RelNotes/1.6.3.txt | 2 +-
 Documentation/RelNotes/1.6.4.txt | 2 +-
 Documentation/RelNotes/1.6.5.txt | 2 +-
 Documentation/RelNotes/1.6.6.txt | 2 +-
 Documentation/RelNotes/1.8.4.txt | 2 +-
 Documentation/RelNotes/2.5.0.txt | 3 ++-
 Documentation/RelNotes/2.8.3.txt | 4 ++--
 Documentation/RelNotes/2.9.0.txt | 2 +-
 9 files changed, 11 insertions(+), 10 deletions(-)
Documentation/RelNotes/1.6.2.txt +1 -1
index ad060f4f89..980adfb315 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.3.txt +1 -1
index 418c685cf8..4bcff945e0 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.4.txt +1 -1
index 7a904419f7..a2a34b43a7 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.5.txt +1 -1
index ee141c19ad..6c7f7da7eb 100644
@@ -22,7 +22,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.6.txt +1 -1
index c50b59c495..3ed1e01433 100644
@@ -64,7 +64,7 @@ users will fare this time.
    Please refer to:
 
    http://git.or.cz/gitwiki/GitFaq#non-bare
-   http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+   https://lore.kernel.org/git/[email protected]/
 
    for more details on the reason why this change is needed and the
    transition process that already took place so far.
Documentation/RelNotes/1.8.4.txt +1 -1
index 02f681b710..255e185af6 100644
@@ -58,7 +58,7 @@ Foreign interfaces, subsystems and ports.
    credential helper interface from Git.pm.
 
  * Update build for Cygwin 1.[57].  Torsten Bögershausen reports that
-   this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
+   this is fine with Cygwin 1.7 (cf. <[email protected]>) so let's try moving it
    ahead.
 
  * The credential helper to talk to keychain on OS X (in contrib/) has
Documentation/RelNotes/2.5.0.txt +2 -1
index 87044504c5..84723f912a 100644
@@ -172,7 +172,8 @@ Performance, Internal Implementation, Development Support etc.
    incorrect patch text to "git apply".  Add tests to demonstrate
    this.
 
-   I have a slight suspicion that this may be $gmane/87202 coming back
+   I have a slight suspicion that this may be
+   cf. <[email protected]> coming back
    and biting us (I seem to have said "let's run with this and see
    what happens" back then).
 
Documentation/RelNotes/2.8.3.txt +0 -0
index fedd9968e5..266c4781a8 100644

Documentation/RelNotes/2.8.3.txt Fixes since v2.8.2 · line 59

Quoted 7 lines
Documentation/RelNotes/2.8.3.txt +2 -2
@@ -55,8 +55,8 @@ Fixes since v2.8.2
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
-   and http://thread.gmane.org/gmane.comp.version-control.git/275680.
+   See https://lkml.org/git/[email protected]/
+   and https://lkml.org/git/[email protected]/.

Brainfart continues here... Wrong URL.

Documentation/RelNotes/2.9.0.txt notes for details). · line 371

Quoted 13 lines
Documentation/RelNotes/2.8.3.txt +0 -0
  * "git replace -e" did not honour "core.editor" configuration.
 
Documentation/RelNotes/2.9.0.txt +1 -1
index b61d36712f..d5f95b6641 100644
@@ -368,7 +368,7 @@ notes for details).
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
+   See https://lkml.org/git/[email protected]/

And here. If Peff's series gets picked up, I'll reroll mine as well.

Quoted 6 lines
Documentation/RelNotes/2.9.0.txt +0 -0
  * "merge-octopus" strategy did not ensure that the index is clean
    when merge begins.
Signature · 1 line
2.24.0.504.g3cd56eb17d
#22 lore raw

Re: [PATCH 0/2] Hi Peff,

In reply to Denton Liu
Quoted 2 lines · Denton Liu

Thanks for doing this. Perhaps while we're at it, we want to change all of the MARC and Gmane links as well? The series below does this.

I suspect that most of the reference you make to LKML should refer to lore.kernel.org instead.

Replacing gmane articule number with the message ID is very much appreciated.

Quoted 21 lines

I've based my series on top of yours so if you need to do a reroll, feel free to pick my changes in.

Denton Liu (2):
doc: replace MARC links with LKML
RelNotes: replace Gmane with real Message-IDs

 Documentation/RelNotes/1.6.2.txt    | 2 +-
 Documentation/RelNotes/1.6.3.txt    | 2 +-
 Documentation/RelNotes/1.6.4.txt    | 2 +-
 Documentation/RelNotes/1.6.5.txt    | 2 +-
 Documentation/RelNotes/1.6.6.txt    | 2 +-
 Documentation/RelNotes/1.8.4.txt    | 2 +-
 Documentation/RelNotes/2.5.0.txt    | 3 ++-
 Documentation/RelNotes/2.8.3.txt    | 4 ++--
 Documentation/RelNotes/2.9.0.txt    | 2 +-
 Documentation/git-bisect-lk2009.txt | 2 +-
 Documentation/gitcli.txt            | 4 ++--
 Documentation/user-manual.txt       | 4 ++--
 t/t6021-merge-criss-cross.sh        | 2 +-
 13 files changed, 17 insertions(+), 16 deletions(-)
#23 lore raw

v2 cover Doc: replace opaque mail archive links with lore.kernel.org

In reply to Denton Liu

We reference many mail archives that use opaque links. Even though many have been around for a long time, they may still be liable to go down (see Gmane) leaving us with dead links that we cannot reference in the future. Replace these links with links to lore.kernel.org which use Message-IDs so that if lore.kernel.org ever goes down, it will be much easier to find these messages in the future.

My series is based on top of 'jk/lore-is-the-archive'.

Denton Liu (3):
doc: replace MARC links with lore.kernel.org
RelNotes: replace Gmane with real Message-IDs
doc: replace LKML link with lore.kernel.org

 Documentation/RelNotes/1.6.2.txt     | 2 +-
 Documentation/RelNotes/1.6.3.txt     | 2 +-
 Documentation/RelNotes/1.6.4.txt     | 2 +-
 Documentation/RelNotes/1.6.5.txt     | 2 +-
 Documentation/RelNotes/1.6.6.txt     | 2 +-
 Documentation/RelNotes/1.8.4.txt     | 2 +-
 Documentation/RelNotes/2.5.0.txt     | 3 ++-
 Documentation/RelNotes/2.8.3.txt     | 4 ++--
 Documentation/RelNotes/2.9.0.txt     | 2 +-
 Documentation/git-bisect-lk2009.txt  | 2 +-
 Documentation/gitcli.txt             | 4 ++--
 Documentation/technical/racy-git.txt | 2 +-
 Documentation/user-manual.txt        | 4 ++--
 t/t6021-merge-criss-cross.sh         | 2 +-
 14 files changed, 18 insertions(+), 17 deletions(-)

Range-diff against v1:
1: 14167012a1 ! 1: 0f100f06c5 doc: replace MARC links with LKML
@@ Metadata
Author: Denton Liu <[email protected]>

## Commit message ##
- doc: replace MARC links with LKML
+ doc: replace MARC links with lore.kernel.org

Since we're now recommending lore.kernel.org, replace marc.info links with lore.kernel.org.

Although MARC has been around for a long time, nothing lasts forever (see Gmane). Since MARC uses opaque message identifiers, switching to
- LKML should be a strict improvement since, even if LKML goes
- down, the Message-ID will allow future readers to look up the referenced
- messages on any other archive.
+ lore.kernel.org should be a strict improvement since, even if
+ lore.kernel.org goes down, the Message-ID will allow future readers to
+ look up the referenced messages on any other archive.

We leave behind one reference to MARC in the README.md since it's a perfectly fine mail archive for personal reading, just not for linking
2: ebb2328a02 ! 2: cad77e0989 RelNotes: replace Gmane with real Message-IDs
@@ Commit message
are definitely not in active use, they might be of historical interest for future readers so let's ensure that mail references are more robust.

- Replace links to Gmane with links to LKML (which is our new preferred
- mailing list archive and has the Message-ID in the URL) and bare Gmane
- ID references with Message-IDs.
+ Replace links to Gmane with links to lore.kernel.org (which is our new
+ preferred mailing list archive and has the Message-ID in the URL) and
+ bare Gmane ID references with Message-IDs.

The Message-IDs were found by searching for "gmane:<id>" on
https://public-inbox.org/git/ and taking the resulting message.
@@ Documentation/RelNotes/2.8.3.txt: Fixes since v2.8.2
has been used in Cygwin packaged versions of Git for quite a while.
- See http://thread.gmane.org/gmane.comp.version-control.git/291853
- and http://thread.gmane.org/gmane.comp.version-control.git/275680.
-+ See https://lkml.org/git/[email protected]/
-+ and https://lkml.org/git/[email protected]/.
++ See https://lore.kernel.org/git/[email protected]/
++ and https://lore.kernel.org/git/[email protected]/.

* "git replace -e" did not honour "core.editor" configuration.

@@ Documentation/RelNotes/2.9.0.txt: notes for details).
already enabled for the MinGW and plain Windows builds. It also has been used in Cygwin packaged versions of Git for quite a while.
- See http://thread.gmane.org/gmane.comp.version-control.git/291853
-+ See https://lkml.org/git/[email protected]/
++ See https://lore.kernel.org/git/[email protected]/

* "merge-octopus" strategy did not ensure that the index is clean when merge begins.
-: ---------- > 3: a7c8981ba5 doc: replace LKML link with lore.kernel.org

Signature · 1 line
2.24.0.504.g3cd56eb17d
#24 lore raw

PATCH v2 1/3 doc: replace MARC links with lore.kernel.org

Since we're now recommending lore.kernel.org, replace marc.info links with lore.kernel.org.

Although MARC has been around for a long time, nothing lasts forever (see Gmane). Since MARC uses opaque message identifiers, switching to lore.kernel.org should be a strict improvement since, even if lore.kernel.org goes down, the Message-ID will allow future readers to look up the referenced messages on any other archive.

We leave behind one reference to MARC in the README.md since it's a perfectly fine mail archive for personal reading, just not for linking messages for the future.

---
 Documentation/git-bisect-lk2009.txt | 2 +-
 Documentation/gitcli.txt            | 4 ++--
 Documentation/user-manual.txt       | 4 ++--
 t/t6021-merge-criss-cross.sh        | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)
Documentation/git-bisect-lk2009.txt +1 -1
index 5bcf4d9b94..72dbe6dbea 100644
@@ -1353,6 +1353,6 @@ References
 - [[[4]]] https://lore.kernel.org/git/[email protected]/[Junio C Hamano. 'Automated bisect success story'.]
 - [[[5]]] https://lwn.net/Articles/317154/[Christian Couder. 'Fully automated bisecting with "git bisect run"'. LWN.net.]
 - [[[6]]] https://lwn.net/Articles/277872/[Jonathan Corbet. 'Bisection divides users and developers'. LWN.net.]
-- [[[7]]] http://marc.info/?l=linux-kernel&m=119702753411680&w=2[Ingo Molnar. 'Re: BUG 2.6.23-rc3 can't see sd partitions on Alpha'. Linux-kernel mailing list.]
+- [[[7]]] https://lore.kernel.org/lkml/[email protected]/[Ingo Molnar. 'Re: BUG 2.6.23-rc3 can't see sd partitions on Alpha'. Linux-kernel mailing list.]
 - [[[8]]] https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html[Junio C Hamano and the git-list. 'git-bisect(1) Manual Page'. Linux Kernel Archives.]
 - [[[9]]] https://github.com/Ealdwulf/bbchop[Ealdwulf. 'bbchop'. GitHub.]
Documentation/gitcli.txt +2 -2
index 1ed3ca33b7..b9cda46a80 100644
@@ -205,8 +205,8 @@ only affects the files in the working tree, but with
 entries, and with `--cached`, it modifies only the index
 entries.
 
-See also http://marc.info/?l=git&m=116563135620359 and
-http://marc.info/?l=git&m=119150393620273 for further
+See also https://lore.kernel.org/git/[email protected]/ and
+https://lore.kernel.org/git/[email protected]/ for further
 information.
 
 Some other commands that also work on files in the working tree and/or
Documentation/user-manual.txt +2 -2
index 8bce75b2cf..2ba5b7a20c 100644
@@ -4687,5 +4687,5 @@ Write a chapter on using plumbing and writing scripts.
 Alternates, clone -reference, etc.
 
 More on recovery from repository corruption.  See:
-	http://marc.info/?l=git&m=117263864820799&w=2
-	http://marc.info/?l=git&m=117147855503798&w=2
+	https://lore.kernel.org/git/[email protected]/
+	https://lore.kernel.org/git/[email protected]/
t/t6021-merge-criss-cross.sh +1 -1
index 213deecab1..d254e020b6 100755
@@ -3,7 +3,7 @@
 # Copyright (c) 2005 Fredrik Kuivinen
 #
 
-# See http://marc.info/?l=git&m=111463358500362&w=2 for a
+# See https://lore.kernel.org/git/[email protected]/ for a
 # nice description of what this is about.
 
 
Signature · 1 line
2.24.0.504.g3cd56eb17d
#25 lore raw

PATCH v2 2/3 RelNotes: replace Gmane with real Message-IDs

In reply to Denton Liu

The only references to Gmane that remain are in RelNotes. Although these are definitely not in active use, they might be of historical interest for future readers so let's ensure that mail references are more robust.

Replace links to Gmane with links to lore.kernel.org (which is our new preferred mailing list archive and has the Message-ID in the URL) and bare Gmane ID references with Message-IDs.

The Message-IDs were found by searching for "gmane:<id>" on
https://public-inbox.org/git/ and taking the resulting message.

---
 Documentation/RelNotes/1.6.2.txt | 2 +-
 Documentation/RelNotes/1.6.3.txt | 2 +-
 Documentation/RelNotes/1.6.4.txt | 2 +-
 Documentation/RelNotes/1.6.5.txt | 2 +-
 Documentation/RelNotes/1.6.6.txt | 2 +-
 Documentation/RelNotes/1.8.4.txt | 2 +-
 Documentation/RelNotes/2.5.0.txt | 3 ++-
 Documentation/RelNotes/2.8.3.txt | 4 ++--
 Documentation/RelNotes/2.9.0.txt | 2 +-
 9 files changed, 11 insertions(+), 10 deletions(-)
Documentation/RelNotes/1.6.2.txt +1 -1
index ad060f4f89..980adfb315 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.3.txt +1 -1
index 418c685cf8..4bcff945e0 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.4.txt +1 -1
index 7a904419f7..a2a34b43a7 100644
@@ -11,7 +11,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.5.txt +1 -1
index ee141c19ad..6c7f7da7eb 100644
@@ -22,7 +22,7 @@ push running this release will issue a big warning when the
 configuration variable is missing.  Please refer to:
 
   http://git.or.cz/gitwiki/GitFaq#non-bare
-  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+  https://lore.kernel.org/git/[email protected]/
 
 for more details on the reason why this change is needed and the
 transition plan.
Documentation/RelNotes/1.6.6.txt +1 -1
index c50b59c495..3ed1e01433 100644
@@ -64,7 +64,7 @@ users will fare this time.
    Please refer to:
 
    http://git.or.cz/gitwiki/GitFaq#non-bare
-   http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
+   https://lore.kernel.org/git/[email protected]/
 
    for more details on the reason why this change is needed and the
    transition process that already took place so far.
Documentation/RelNotes/1.8.4.txt +1 -1
index 02f681b710..255e185af6 100644
@@ -58,7 +58,7 @@ Foreign interfaces, subsystems and ports.
    credential helper interface from Git.pm.
 
  * Update build for Cygwin 1.[57].  Torsten Bögershausen reports that
-   this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
+   this is fine with Cygwin 1.7 (cf. <[email protected]>) so let's try moving it
    ahead.
 
  * The credential helper to talk to keychain on OS X (in contrib/) has
Documentation/RelNotes/2.5.0.txt +2 -1
index 87044504c5..84723f912a 100644
@@ -172,7 +172,8 @@ Performance, Internal Implementation, Development Support etc.
    incorrect patch text to "git apply".  Add tests to demonstrate
    this.
 
-   I have a slight suspicion that this may be $gmane/87202 coming back
+   I have a slight suspicion that this may be
+   cf. <[email protected]> coming back
    and biting us (I seem to have said "let's run with this and see
    what happens" back then).
 
Documentation/RelNotes/2.8.3.txt +2 -2
index fedd9968e5..a63825ed87 100644
@@ -55,8 +55,8 @@ Fixes since v2.8.2
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
-   and http://thread.gmane.org/gmane.comp.version-control.git/275680.
+   See https://lore.kernel.org/git/[email protected]/
+   and https://lore.kernel.org/git/[email protected]/.
 
  * "git replace -e" did not honour "core.editor" configuration.
 
Documentation/RelNotes/2.9.0.txt +1 -1
index b61d36712f..991640119a 100644
@@ -368,7 +368,7 @@ notes for details).
    This is necessary to use Git on Windows shared directories, and is
    already enabled for the MinGW and plain Windows builds.  It also
    has been used in Cygwin packaged versions of Git for quite a while.
-   See http://thread.gmane.org/gmane.comp.version-control.git/291853
+   See https://lore.kernel.org/git/[email protected]/
 
  * "merge-octopus" strategy did not ensure that the index is clean
    when merge begins.
Signature · 1 line
2.24.0.504.g3cd56eb17d
#26 lore raw

PATCH v2 3/3 doc: replace LKML link with lore.kernel.org

In reply to Denton Liu

Since we're now recommending lore.kernel.org, replace LKML link with lore.kernel.org.

Although LKML has been around for a long time, nothing lasts forever (see Gmane). Since LKML uses opaque message identifiers, switching to lore.kernel.org should be a strict improvement since, even if lore.kernel.org goes down, the Message-ID will allow future readers to look up the referenced messages on any other archive.

---
 Documentation/technical/racy-git.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/technical/racy-git.txt +1 -1
index 4a8be4d144..ceda4bbfda 100644
@@ -51,7 +51,7 @@ of git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
 only fixes the issue for file systems with exactly 1 ns or 1 s
 resolution. Other file systems are still broken in current Linux
 kernels (e.g. CEPH, CIFS, NTFS, UDF), see
-https://lkml.org/lkml/2015/6/9/714
+https://lore.kernel.org/lkml/[email protected]/
 
 Racy Git
 --------
Signature · 1 line
2.24.0.504.g3cd56eb17d
#27 lore raw

Re: [PATCH v2 0/3] Doc: replace opaque mail archive links with lore.kernel.org

In reply to Denton Liu

It must have taken some tedious manual work to figure out the original message IDs, but the end result that uses the message IDs would have a lot better longevity than the original.

Thanks for working on this; will queue (on top of peff's topic).