From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sebastian Fricke <sebastian.fricke@collabora.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hverkuil-cisco@xs4all.nl, mauro.chehab@linux.intel.com,
kernel@collabora.com, bob.beckett@collabora.com,
nicolas.dufresne@collabora.com
Subject: Re: [PATCH 0/2] Documentation: Debugging guide
Date: Fri, 8 Nov 2024 15:58:49 +0700 [thread overview]
Message-ID: <Zy3SybM9e84LmgFo@archie.me> (raw)
In-Reply-To: <20241108082416.u6vvdmmhadfqtiau@basti-XPS-13-9310>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Fri, Nov 08, 2024 at 09:24:16AM +0100, Sebastian Fricke wrote:
> Hmmm my Google-Fu is not strong enough, I can't find a docs-next
> anywhere neither in https://git.kernel.org/ nor in the Linux Kernel
> documentation, can you point me to the tree?
git fetch git://git.lwn.net/linux.git docs-next
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-08 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 14:00 [PATCH 0/2] Documentation: Debugging guide Sebastian Fricke
2024-11-07 14:00 ` [PATCH 1/2] docs: Add guides section for debugging Sebastian Fricke
2024-11-07 20:35 ` Jonathan Corbet
2024-11-07 21:23 ` Randy Dunlap
2024-11-08 8:13 ` Sebastian Fricke
2024-11-08 16:40 ` Jonathan Corbet
2024-11-09 0:10 ` Bagas Sanjaya
2024-11-11 9:46 ` Sebastian Fricke
2024-11-07 14:00 ` [PATCH 2/2] docs: media: Debugging guide for the media subsystem Sebastian Fricke
2024-11-07 20:40 ` Jonathan Corbet
2024-11-08 10:12 ` Sebastian Fricke
2024-11-11 9:50 ` Sebastian Fricke
2024-11-11 14:57 ` Jonathan Corbet
2024-11-07 14:03 ` [PATCH 0/2] Documentation: Debugging guide Sebastian Fricke
2024-11-07 16:45 ` Jonathan Corbet
2024-11-07 17:57 ` Sebastian Fricke
2024-11-08 8:24 ` Sebastian Fricke
2024-11-08 8:58 ` Bagas Sanjaya [this message]
2024-11-08 14:45 ` Jonathan Corbet
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=Zy3SybM9e84LmgFo@archie.me \
--to=bagasdotme@gmail.com \
--cc=bob.beckett@collabora.com \
--cc=corbet@lwn.net \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mauro.chehab@linux.intel.com \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.fricke@collabora.com \
/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 NNTP newsgroup(s).