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

Re: Pingback/Trackback for Git?

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 4, 2007, 05:10 UTC
Message-ID
<7vbqeslpnz.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<372f54da0707030512k79e2dc74m98bf0a690abffc4a@mail.gmail.com>
"Thomas Perl" <th.perl@gmail.com> writes:
> I've outlined some ideas here, feel free to suggest implementations or
> point out problems:
>
> http://tperl.blogspot.com/2007/07/pingbacktrackback-for-git.html

It was unclear to me who does what and when in the overall picture you envision after reading that page. You seem to assume there is a prominent ping/trackback repository that everybody who is interested looks at. Who updates it? When? With what? How does the namespace inside that repository managed, if managed in any way? Given a project name, how does one learn which pick/grackback repository (and perhaps which branch) to go to to learn the current status about it?

Previous: Thomas PerlNext: Thomas Perl
Message 2 of 3 in “Pingback/Trackback for Git?”
  1. Thomas PerlJul 3, 2007
  2. Junio C HamanoJul 4, 2007
  3. Thomas PerlJul 4, 2007

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.