git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Tagging Commits] feedback / discussion request

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
May 5, 2011, 18:49 UTC
Message-ID
<BANLkTinKLnsVp50+d_7U_vSUiaMNtZ-NCA@mail.gmail.com>
In-Reply-To
<BANLkTinCxzXCmmtxXSM7=+yeve2hhLSYNQ@mail.gmail.com>
Heya,
On Thu, May 5, 2011 at 17:39, Richard Peterson <richard@rcpeterson.com> wrote:
> Now my big question to ponder: what do do when the CA expires a cert? Hmm...

You could re-sign the commits with the new cert, notes are mutable, and they keep history too. So you could just create a commit on the notes history ref "re-sign commits for expired cert", optionally removing the old signature. The hook verifying that no-one is tampering with the notes might get complex if you do that kind of stuff though (might be easier to just append the new signature and keep the old one in place).

-- 
Cheers,

Sverre Rabbelier
Previous: Richard PetersonNext: Jeff King
Message 6 of 7 in “[Tagging Commits] feedback / discussion request”
  1. Richard PetersonMay 3, 2011
  2. Sverre RabbelierMay 3, 2011
  3. Michael J GruberMay 4, 2011
  4. Jeff KingMay 4, 2011
  5. Richard PetersonMay 5, 2011
  6. Sverre RabbelierMay 5, 2011
  7. Jeff KingMay 5, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.