linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Eric Van Hensbergen <ericvh@kernel.org>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Docs/filesystems/9p: Convert a goo.gl URL to original one
Date: Sun, 25 Aug 2024 19:21:29 -0700	[thread overview]
Message-ID: <20240826022129.81139-1-sj@kernel.org> (raw)
In-Reply-To: <ZsvX90dovlI52Ohd@codewreck.org>

On Mon, 26 Aug 2024 10:18:47 +0900 Dominique Martinet <asmadeus@codewreck.org> wrote:

> SeongJae Park wrote on Sun, Aug 25, 2024 at 06:09:49PM -0700:
> > Google URL shortner will be unavailable soon[1].  Replace a shortened
> > URL on 9p.rst with its original one.
> > 
> > [1] https://developers.googleblog.com/en/google-url-shortener-links-will-no-longer-be-available/
> > 
> > Signed-off-by: SeongJae Park <sj@kernel.org>
> 
> Sorry, we (9p maintainers) slacked on this one - there's been a better
> patch for this one:
> https://lkml.kernel.org/r/20240725180041.80862-1-linux@treblig.org
> 
> The sciweavers link doesn't actually work, so it doesn't make sense to
> replace as is.
> (although you could argue that it's probably been broken forever an
> nobody noticed, so it could just as well be removed...)

No problem.  I agree the other patch is better.

> 
> There's no patch queued for 9p, so if you (Jonathan) want to take the
> other patch please feel free to.
> If it goes through the 9p tree it'll get in the next time we send
> something as I don't feel the need to send Linus a PR just for this, so
> that might be a couple of months further down.

Either ways look good to me.

> (I don't like patch series where folks are added in Cc on individual
> patches because it's never clear who is expected to grab the patch in
> the end...)

Sorry for that.  I thoght lore.kernel.org should help getting the context, but
I understand no one can convince all.  I'll try to take a different approach if
I have a chance to send patches to you next time.


Thanks,
SJ

> 
> 
> Thanks,
> -- 
> Dominique

  reply	other threads:[~2024-08-26  2:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  1:09 [PATCH 1/3] Docs/translations/ko_KR: link howto.rst with other language versions SeongJae Park
2024-08-26  1:09 ` [PATCH 2/3] Docs/translations/ko_KR: link memory-barriers wrapper " SeongJae Park
2024-08-26  1:09 ` [PATCH 3/3] Docs/filesystems/9p: Convert a goo.gl URL to original one SeongJae Park
2024-08-26  1:18   ` Dominique Martinet
2024-08-26  2:21     ` SeongJae Park [this message]
2024-08-26 22:41     ` Jonathan Corbet
2024-08-26 22:39 ` [PATCH 1/3] Docs/translations/ko_KR: link howto.rst with other language versions 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=20240826022129.81139-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=asmadeus@codewreck.org \
    --cc=corbet@lwn.net \
    --cc=ericvh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=v9fs@lists.linux.dev \
    /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).