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

Re: Why does gpg.program work for commit but not log?

From
Jeff King <peff@peff.net>
Date
Jun 18, 2014, 12:51 UTC
Message-ID
<20140618125116.GA7753@sigill.intra.peff.net>
In-Reply-To
<9B9CF0F915BD4325BC92BBA1339B1B4E@black>
On Wed, Jun 18, 2014 at 08:38:32AM -0400, Jason Pyeron wrote:
Show 6 quoted lines
> > That's rather old. In the meantime we have:
> > 
> > 	commit 6005dbb9bf21d10b209f7924e305bd04b9ab56d2
> [...]
> 
> I will (try to) compile master and test. This is the latest version in cygwin.

To save you some trouble, I actually found that commit by reproducing your problem on Linux and bisecting. So I'm fairly sure it will fix it for you. :)

You may want to bug the cygwin packagers about updating their version of git. v1.7.9 is two and a half years old, and since then we have many bugfixes, including some which are specifically targeted at cygwin (which can only lead me to assume a lot of people are building from source on cygwin).

-Peff
Previous: Jason PyeronNext: Jason Pyeron
Message 4 of 5 in “Why does gpg.program work for commit but not log?”
  1. Jason PyeronJun 18, 2014
  2. Jeff KingJun 18, 2014
  3. Jason PyeronJun 18, 2014
  4. Jeff KingJun 18, 2014
  5. Jason PyeronJun 18, 2014

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.