如何读取 git-ls-tree 输出的模式字段

发布于 2024-07-16 07:04:40 字数 648 浏览 4 评论 0原文

$ git ls-tree fb3a8bdd0ce
100644 blob 63c918c667fa005ff12ad89437f2fdc80926e21c    .gitignore
100644 blob 5529b198e8d14decbe4ad99db3f7fb632de0439d    .mailmap
100644 blob 6ff87c4664981e4397625791c8ea3bbb5f2279a3    COPYING
040000 tree 2fb783e477100ce076f6bf57e4a6f026013dc745    Documentation
100755 blob 3c0032cec592a765692234f1cba47dfdcc3a9200    GIT-VERSION-GEN
100644 blob 289b046a443c0647624607d471289b2c7dcd470b    INSTALL
100644 blob 4eb463797adc693dc168b926b6932ff53f17d0b1    Makefile
100644 blob 548142c327a6790ff8821d67c2ee1eff7a656b52    README
...

我知道最后 3 个八进制数字是文件模式,但是前 3 个数字是做什么用的? 我在 git 用户手册中找不到它。

$ git ls-tree fb3a8bdd0ce
100644 blob 63c918c667fa005ff12ad89437f2fdc80926e21c    .gitignore
100644 blob 5529b198e8d14decbe4ad99db3f7fb632de0439d    .mailmap
100644 blob 6ff87c4664981e4397625791c8ea3bbb5f2279a3    COPYING
040000 tree 2fb783e477100ce076f6bf57e4a6f026013dc745    Documentation
100755 blob 3c0032cec592a765692234f1cba47dfdcc3a9200    GIT-VERSION-GEN
100644 blob 289b046a443c0647624607d471289b2c7dcd470b    INSTALL
100644 blob 4eb463797adc693dc168b926b6932ff53f17d0b1    Makefile
100644 blob 548142c327a6790ff8821d67c2ee1eff7a656b52    README
...

I know the last 3 oct digits are file mode, but what are the first 3 digits for?
I can't find it out in git user's manual.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

肩上的翅膀 2024-07-23 07:04:40

来自 gitformat -index(5) / 参考文档Git 索引文件格式 (1, ²),关于模式:

32-bit mode, split into (high to low bits)

    4-bit object type
      valid values in binary are 1000 (regular file), 1010 (symbolic link)
      and 1110 (gitlink)

    3-bit unused

    9-bit unix permission. Only 0755 and 0644 are valid for regular files.
    Symbolic links and gitlinks have value 0 in this field.

此外,还允许目录对象类型(二进制 0100)和组可写(0664 权限)常规文件,如 fsck.c fsck_tree 方法。 常规的不可执行的组可写文件是早期版本的 Git 支持的非标准模式。

这使得有效模式(二进制和八进制):

  • 0100000000000000 (040000): Directory
  • 1000000110100100 (100644):常规非可执行文件
  • 1000000110110100 (100664):常规非可执行组可写文件
  • 1000000111101101 (100755) :常规可执行文件
  • 1010000000000000 (120000):符号链接
  • 1110000000000000 (160000):Gitlink

  1. (源)文档:将索引格式文档移至 man 第 5 节 — 00d3e8d
  2. (Microsoft Github 上的存档副本) 文档:将索引格式文档移至 man 部分 5 — 00d3e8d

From gitformat-index(5) / the Reference Documentations The Git index file format (¹, ²), regarding the mode:

32-bit mode, split into (high to low bits)

    4-bit object type
      valid values in binary are 1000 (regular file), 1010 (symbolic link)
      and 1110 (gitlink)

    3-bit unused

    9-bit unix permission. Only 0755 and 0644 are valid for regular files.
    Symbolic links and gitlinks have value 0 in this field.

Also, a directory object type (binary 0100) and group-writeable (0664 permissions) regular file are allowed as indicated by the fsck.c fsck_tree method. The regular non-executable group-writeable file is a non-standard mode that was supported in earlier versions of Git.

This makes valid modes (as binary and octal):

  • 0100­000­000000000 (040000): Directory
  • 1000­000­110100100 (100644): Regular non-executable file
  • 1000­000­110110100 (100664): Regular non-executable group-writeable file
  • 1000­000­111101101 (100755): Regular executable file
  • 1010­000­000000000 (120000): Symbolic link
  • 1110­000­000000000 (160000): Gitlink

  1. (Source) docs: move index format docs to man section 5 — 00d3e8d
  2. (Archived copy on Microsoft Github) docs: move index format docs to man section 5 — 00d3e8d
呆橘 2024-07-23 07:04:40

6 位数字使用经典 UNIX 表示法显示文件模式。
前两位数字显示文件类型,第三位数字与 set-uid/set-gid/sticky 位有关,最后三位数字您也知道。

以下是 man 2 stat 在我的 GNU/Linux 系统上如何记录它:

   The following flags are defined for the st_mode field:

       S_IFMT     0170000   bit mask for the file type bit fields
       S_IFSOCK   0140000   socket
       S_IFLNK    0120000   symbolic link
       S_IFREG    0100000   regular file
       S_IFBLK    0060000   block device
       S_IFDIR    0040000   directory
       S_IFCHR    0020000   character device
       S_IFIFO    0010000   FIFO
       S_ISUID    0004000   set UID bit
       S_ISGID    0002000   set-group-ID bit (see below)
       S_ISVTX    0001000   sticky bit (see below)
       S_IRWXU    00700     mask for file owner permissions
       S_IRUSR    00400     owner has read permission
       S_IWUSR    00200     owner has write permission
       S_IXUSR    00100     owner has execute permission
       S_IRWXG    00070     mask for group permissions
       S_IRGRP    00040     group has read permission
       S_IWGRP    00020     group has write permission
       S_IXGRP    00010     group has execute permission
       S_IRWXO    00007     mask for permissions for others (not in group)
       S_IROTH    00004     others have read permission           
       S_IWOTH    00002     others have write permission
       S_IXOTH    00001     others have execute permission

The 6 digits show the file mode using the classical UNIX notations.
First two digits show file type, the third one is about set-uid/set-gid/sticky bits, and you know the last three.

Here is how man 2 stat documents it on my GNU/Linux system:

   The following flags are defined for the st_mode field:

       S_IFMT     0170000   bit mask for the file type bit fields
       S_IFSOCK   0140000   socket
       S_IFLNK    0120000   symbolic link
       S_IFREG    0100000   regular file
       S_IFBLK    0060000   block device
       S_IFDIR    0040000   directory
       S_IFCHR    0020000   character device
       S_IFIFO    0010000   FIFO
       S_ISUID    0004000   set UID bit
       S_ISGID    0002000   set-group-ID bit (see below)
       S_ISVTX    0001000   sticky bit (see below)
       S_IRWXU    00700     mask for file owner permissions
       S_IRUSR    00400     owner has read permission
       S_IWUSR    00200     owner has write permission
       S_IXUSR    00100     owner has execute permission
       S_IRWXG    00070     mask for group permissions
       S_IRGRP    00040     group has read permission
       S_IWGRP    00020     group has write permission
       S_IXGRP    00010     group has execute permission
       S_IRWXO    00007     mask for permissions for others (not in group)
       S_IROTH    00004     others have read permission           
       S_IWOTH    00002     others have write permission
       S_IXOTH    00001     others have execute permission
烟花肆意 2024-07-23 07:04:40

添加到 Go Dan答案,Git 2.40(2023 年第一季度)添加:

请参阅提交 3a2ebae(2023 年 2 月 1 日)作者:Glen Choo (chooglen)
(由 Junio C Hamano -- gitster -- 合并于 提交 2c91b13,2023 年 2 月 9 日)

docs:索引中的文档零位“模式”

签字人:Glen Choo

文档/gitformat- index.txt将“模式”描述为32位,但仅记录16位。

记录缺失的 16 位并指定“未使用”位必须为零。

gitformat-index 现在包含在其 手册页

16 位未使用,必须为零
...
3 位未使用,必须为零

这意味着格式实际上是:

  • 0(16x) 0100 000 000000000 (040000): Directory
  • 0(16x) 1000 000 110100100 (100644):常规非可执行文件
  • 0(16x) 1000 000 110110100 (100664):常规非可执行文件组可写文件
  • 0(16x) 1000 000 111101101 (100755):常规可执行文件
  • 0(16x) 1010 000 000000000 (120000): 符号链接
  • 0(16x) 1110 000 000000000 (160000): Gitlink
  • ^^^
  • 始终设置到0

To add to Go Dan's answer, Git 2.40 (Q1 2023) adds:

See commit 3a2ebae (01 Feb 2023) by Glen Choo (chooglen).
(Merged by Junio C Hamano -- gitster -- in commit 2c91b13, 09 Feb 2023)

docs: document zero bits in index "mode"

Signed-off-by: Glen Choo

Documentation/gitformat-index.txt describes the "mode" as 32 bits, but only documents 16 bits.

Document the missing 16 bits and specify that 'unused' bits must be zero.

gitformat-index now includes in its man page:

16-bit unused, must be zero
...
3-bit unused, must be zero

Which means the format actually is:

  • 0(16x) 0100 000 000000000 (040000): Directory
  • 0(16x) 1000 000 110100100 (100644): Regular non-executable file
  • 0(16x) 1000 000 110110100 (100664): Regular non-executable group-writeable file
  • 0(16x) 1000 000 111101101 (100755): Regular executable file
  • 0(16x) 1010 000 000000000 (120000): Symbolic link
  • 0(16x) 1110 000 000000000 (160000): Gitlink
  • ^^^
  • always set to 0
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文