[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221027204401.GA838114@bhelgaas>
Date: Thu, 27 Oct 2022 15:44:01 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: "Limonciello, Mario" <mario.limonciello@....com>
Cc: Lukas Wunner <lukas@...ner.de>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Mehta Sanju <Sanju.Mehta@....com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] PCI/ACPI: PCI/ACPI: Validate devices with power
resources support D3
On Thu, Oct 27, 2022 at 02:56:19PM -0500, Limonciello, Mario wrote:
> On 10/27/2022 00:24, Lukas Wunner wrote:
> > ...
> > I think git.kernel.org links are preferred to 3rd party hosting services.
>
> I wasn't aware of any such policy. Within the last release it seemed to me
> Github was perfectly acceptable to use for links.
>
> $ git log v6.0..v6.1-rc1 | grep "Link: https://github" | wc -l
> 107
> $ git log v6.0..v6.1-rc1 | grep "Link: https://git.kernel.org" | wc -l
> 2
I'm not aware of a formal policy, but I do prefer kernel.org links
because github is a 3rd party company that may not persist, may add
ads, etc. I know github may *also* add value like fancier markup,
cross referencing, CI services, etc., but for commit logs, the
longevity of kernel.org is pretty persuasive to me.
There's a similar situation with mailing lists where many of the old
links to archives like marc.info, spinics.net, lkml.org, etc., are now
dead or not as useful for building tools (b4, for instance).
So no big deal, but I would probably silently convert them when
applying. The current formats I use are:
commits: https://git.kernel.org/linus/dff6139015dc
files: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pci-acpi.c?id=v6.0#n976
Bjorn
Powered by blists - more mailing lists