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

Re: [GSoC][RFC] discussion about stashing with conflicts

From
Duy Nguyen <pclouds@gmail.com>
Date
Apr 8, 2019, 11:09 UTC
Message-ID
<CACsJy8D7mQZgJhZ4H8Z929EnjYe1Wp7idrbXqkUsmL1Ypn83dg@mail.gmail.com>
In-Reply-To
<CAMknYENqH==YcAfU-B16Jytc4Pts4viNQn9deTFag++zZVb1+Q@mail.gmail.com>
On Mon, Apr 8, 2019 at 6:00 PM Kapil Jain <jkapil.cs@gmail.com> wrote:
> for finding that commit message did you do something like this:
> git log -L :repo_read_index_unmerged:read-cache.c

No. I'm old fashioned. I just do "git log --patch --follow <path>" then search read_index_unmerged, which should at least appear in the @@ line. But yeah log -L or "tig blame" may be better to dig in history.

-- 
Duy
Previous: Kapil JainNext: Kapil Jain
Message 6 of 8 in “[GSoC][RFC] discussion about stashing with conflicts”
  1. Kapil JainApr 7, 2019
  2. Thomas GummererApr 7, 2019
  3. Kapil JainApr 8, 2019
  4. Duy NguyenApr 8, 2019
  5. Kapil JainApr 8, 2019
  6. Duy NguyenApr 8, 2019
  7. Kapil JainApr 8, 2019
  8. Thomas GummererApr 8, 2019

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.