linux-kernel - Re: [git pull] work.fd fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 5 Jun 2022 17:15:13 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] work.fd fix

On Sun, Jun 5, 2022 at 12:13 PM Al Viro <viro@...iv.linux.org.uk> wrote:
>
> [BTW, what conventions are generally used for pull tag names?]

I don't think we have conventions.

There's a few common patterns, where the tag-name might be the
subsystem name, followed by the version number, followed by a possible
sequential tag number. So "acpi-5.17-rc1-3" or "powerpc-5.16-1" or
"net-5.15-rc8" or "mtd/fixes-for-5.14-rc7".

But another common pattern is to just re-use the same tag-name over
and over again, just updating the tag: "arm64-fixes" or
"clk-fixes-for-linus" or whatever.

In fact, the most common tag-name is just some variation of
"for-linus" (variations: "fixes-for-linus", "for_linus",
"hwmon-for-linus" etc etc)

It really doesn't matter, and your "pull-work.fd-fixes" name is fine.

                  Linus