public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: наб <nabijaczleweli@nabijaczleweli.xyz>, linux-man@vger.kernel.org
Subject: Re: [PATCH] tmpfs.5: document size/blocks=0 and nr_inodes=0 <=> unlimited
Date: Sat, 12 Aug 2023 22:48:58 +0200	[thread overview]
Message-ID: <40ecd524-8914-1dac-ef85-130cedd799a3@kernel.org> (raw)
In-Reply-To: <20230812190401.4bf7xay4fws43tza@jwilk.net>


[-- Attachment #1.1: Type: text/plain, Size: 1420 bytes --]

On 2023-08-12 21:04, Jakub Wilk wrote:
> * Alejandro Colomar <colomar.6.4.3@gmail.com>, 2023-08-12 20:08:
>>> Bitten by this again. Behaviour blames back to at least 2005 (so 
>>> probably original to shmem.c), documented upstream in tmpfs.txt.
> 
> (I've been bitten by this too!)
> 
>> This is a bit unclear to me.  I guess you refer to the Linux kernel as 
>> "upstream", but the Linux kernel repository doesn't have a tmpfs.txt 
>> file.  I recall that they moved their .txt docs to .rst, so would you 
>> please share the full link to the .txt file that you refer?  That way 
>> you can ask git(1) to show the history of that file even if it doesn't 
>> exist now.
> 
> You can ask git for history of tmpfs.txt even if you don't know the 
> exact location, although admittedly it's pretty slow:
> 
>     $ git log --oneline -1 '**/tmpfs.txt'
>     7e7cd458b810 docs: filesystems: convert tmpfs.txt to ReST
> 
>     $ git show --oneline --stat 7e7cd458b810
>     7e7cd458b810 docs: filesystems: convert tmpfs.txt to ReST
>      Documentation/filesystems/index.rst                |  1 +
>      Documentation/filesystems/{tmpfs.txt => tmpfs.rst} | 44 +++++++++++++++++++++++++++++---------------
>      2 files changed, 30 insertions(+), 15 deletions(-)

Interesting.  Thanks!

> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2023-08-12 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 13:41 [PATCH] tmpfs.5: document size/blocks=0 and nr_inodes=0 <=> unlimited наб
2023-08-12 18:08 ` Alejandro Colomar
2023-08-12 19:04   ` Jakub Wilk
2023-08-12 20:03     ` [PATCH v2] " наб
2023-08-12 20:49       ` Alejandro Colomar
2023-08-12 20:48     ` Alejandro Colomar [this message]

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=40ecd524-8914-1dac-ef85-130cedd799a3@kernel.org \
    --to=alx@kernel.org \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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