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

Re: git log reliability

From
TCTomas Carnecky <tomas.carnecky@gmail.com>
Date
Dec 17, 2012, 09:38 UTC
Message-ID
<1355737102-ner-5842@calvin>
In-Reply-To
<CANirugRmpoGb=T1V2ZBw3GEE5nYwD-hyLOfWgt-UVvMXh-i_OA@mail.gmail.com>
On Mon, 17 Dec 2012 14:56:17 +0530, Prasad Karmarkar <prasad.s.karmarkar@gmail.com> wrote:
Show 7 quoted lines
> Hi ,
> 
> I have been hearing from my Release Management that git log is not
> reliable. Is it so ?
> Is there a known instance where Git log has missed out on commits ?
> 
> Any information about this would be really helpful

Are you talking about git skipping commits due to history simplification (read the corresponding section in the git-log man page)?

Also, what for does your release management use git log? Maybe there is a better way to do what you need to do.

Previous: Prasad Karmarkar
Message 2 of 2 in “git log reliability”
  1. Prasad KarmarkarDec 17, 2012
  2. Tomas CarneckyDec 17, 2012

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.