Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: "Matthias Aßhauer" <mha1993@live.de>
To: Jeff King <peff@peff.net>
Cc: Elsie Hupp <git@elsiehupp.com>,
	Junio C Hamano <gitster@pobox.com>,
	reto@labrat.space, philipoakley@iee.email, git@vger.kernel.org
Subject: Re: Multiple --global config workspaces?
Date: Sat, 15 Oct 2022 12:56:38 +0200 (CEST)	[thread overview]
Message-ID: <AM0PR04MB60197E29A9D11F3689C03225A5279@AM0PR04MB6019.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <Y0m64fHWIjZoXoTQ@coredump.intra.peff.net>



On Fri, 14 Oct 2022, Jeff King wrote:

> I'm not sure who to poke about updating those other sites (or even how
> old they are). The git-scm.com is maintained by Git folks, and always
> has documentation for the latest version. It also shows up at the top of
> Google results for me, but given how personalization works there, I've
> no clue how common that is.

die.net is often quite high in the google results for me and from 
experience seems to be a common source when looking up man pages online.
Their git related man pages seem to be roughly from around Git 1.7.5. 
They do have a contact email at the bottom of their homepage. I'll try to 
poke them.

Best regards

Matthias

  reply	other threads:[~2022-10-15 10:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  3:06 Multiple --global config workspaces? Elsie Hupp
2022-10-11  5:50 ` Junio C Hamano
2022-10-11 13:13   ` Jeff King
2022-10-11 16:55     ` Elsie Hupp
2022-10-11 18:41       ` Elsie Hupp
2022-10-14 19:39       ` Jeff King
2022-10-15 10:56         ` Matthias Aßhauer [this message]
2022-10-15 18:14           ` Jeff King
2022-10-18  4:02         ` Elsie Hupp
2022-10-18 20:53           ` Jeff King
2022-10-20  2:29             ` Elsie Hupp
2022-10-20  2:39               ` Elsie Hupp
2022-10-11 13:56   ` Philip Oakley
2022-10-11  5:51 ` Reto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM0PR04MB60197E29A9D11F3689C03225A5279@AM0PR04MB6019.eurprd04.prod.outlook.com \
    --to=mha1993@live.de \
    --cc=git@elsiehupp.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=philipoakley@iee.email \
    --cc=reto@labrat.space \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).