Warner Losh wrote in <CANCZdfpcohhZ4vxWz3OxNcJAYS6X0qpVZMGAc75m=3ogXZw0kg_at_mail.gmail.com>: |On Mon, Sep 21, 2020 at 2:55 PM Steffen Nurpmeso <steffen_at_sdaoden.eu> \ |wrote: |> Lev Serebryakov wrote in |> <23e7fc1c-6769-ceaf-4089-46e5cc575c20_at_FreeBSD.org>: |>|On 19.09.2020 19:05, Bakul Shah wrote: |>|>> These are the main ones. The three down sides are lack of $FreeBSD$ \ |>|>> support |>|>> and tags in general. |>|> |>|> Can a git hook be used for this? |>| |>|git filters could be used for that, problem is it should be local config\ |>|uration. You could not configure filters in clones automatically :-( |> |> I do not think you can do that. Once i switched to git (2011 or |> a bit before) i even looked around for this, because i have been |> educated by BSD and used such tags everywhere, and found a thread |> with the Linus from where the elks live regarding this topic. |> I guess that $SHA-1$ git (supported by git by then) is the outcome |> of this thread, offered as a compromise. That mail thread exists. |> | |It's documented to be the hash of the blob, not the hash of the commit., |which makes it basically useless for our purposes... Never used that. Even if it requires additional tooling and/or the repository, whereas the BSD way is that you can take such a freely licensed file, include it somewhere, and strings(1) etc. still gives you an immediately human graspable output. I mean, if the project agrees by policy then of course the master copy at freebsd.org can expand such things when commits are merged. There are now also many more hooks available, in fact i have no idea of what i am talking about ^_^ --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)Received on Mon Sep 21 2020 - 20:31:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC