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

Re: Feature suggestion: git-hist

From
LNLars Noschinski <lars-2008-1@usenet.noschinski.de>
Date
Jul 30, 2008, 13:33 UTC
Message-ID
<20080730133334.GB31192@lars.home.noschinski.de>
In-Reply-To
<20080730133859.368bbd92@pc09.procura.nl>
* H.Merijn Brand <h.m.brand@xs4all.nl> [08-07-30 13:38]:
Show 8 quoted lines
>	I can ask them what version they have, and I can then check if
>	the complaint was already addressed in an update that was
>	already released. In SCCS this was easy: they tell me the output
>	of the what command, I check if the bug was fixed in a newer
>	version and the answer is present. No such luck in git, as the
>	stamps are (non-sequitive) SHA id's. As we moved to git, we now
>	have to update those id's by hand, as the customers are used to
>	it. (At least we can now use readable date formats)
Hm, what about "git-describe --contains $SHA_OF_BUGFIX"?
Previous: H.Merijn BrandNext: H.Merijn Brand
Message 4 of 13 in “Feature suggestion: git-hist”
  1. H.Merijn BrandJul 30, 2008
  2. Pieter de BieJul 30, 2008
  3. H.Merijn BrandJul 30, 2008
  4. Lars NoschinskiJul 30, 2008
  5. H.Merijn BrandJul 30, 2008
  6. Miklos VajnaJul 30, 2008
  7. H.Merijn BrandJul 30, 2008
  8. Santi BéjarJul 30, 2008
  9. Avery PennarunJul 30, 2008
  10. Lars NoschinskiJul 30, 2008
  11. Santi BéjarJul 30, 2008
  12. H.Merijn BrandJul 30, 2008
  13. H.Merijn BrandJul 30, 2008

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.