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

Re: [PROPOSAL] Add a module (repo-log.c) to log repository events.

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jun 16, 2005, 09:04 UTC
Message-ID
<2cfc403205061602046ec3f430@mail.gmail.com>
In-Reply-To
<2cfc4032050615210961c4d146@mail.gmail.com>
On 6/16/05, Jon Seymour <jon.seymour@gmail.com> wrote:
Show 7 quoted lines
> A variety of log formats would be possible but the default log format
> I intend to use is:
> 
> for object events:
> 
>      yy-mm-ddThh:mm:ss(+/-)oooo SP object-type SP sha1  LF
> 
Further enhancements along these lines:
      yy-mm-ddThh:mm:ss(+/-)oooo SP object-type SP sha1 [ SP name ]  LF

This will require more invasive instrumentation but when a blob is written it will allow the name with which the blob was known to be logged, if that is known. Of course, this name may not survive over time, but it was accurate at the time of the the repo event.

The objective of doing this, of course, is to allow a git user to quickly find a blob or tree that was accidentally "lost", by scanning the repo log.

jon.
Previous: Jon Seymour
Message 3 of 3 in “[PROPOSAL] Add a module (repo-log.c) to log repository events.”
  1. 1/1 [PROPOSAL] Add a module (repo-log.c) to log repository events.Jon Seymour, Jun 16, 2005
  2. [PROPOSAL] Add a module (repo-log.c) to log repository events.Jon Seymour, Jun 16, 2005
  3. Jon SeymourJun 16, 2005

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.