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

Re: [PATCH v4 4/6] patch-id: make it stable against hunk reordering

From
MTMichael S. Tsirkin <mst@redhat.com>
Date
Apr 23, 2014, 17:57 UTC
Message-ID
<20140423175717.GB28308@redhat.com>
In-Reply-To
<xmqq4n1k0wtw.fsf@gitster.dls.corp.google.com>
On Wed, Apr 23, 2014 at 10:39:23AM -0700, Junio C Hamano wrote:
> Are these three patches the same as what has been queued on
> mt/patch-id-stable topic and cooking in 'next' for a few weeks?

Not exactly - at your request I implemented git config options to control patch id behaviour. Documentation and tests updated to match.

Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 15 in “diff: add a config option to control orderfile”
  1. 1/6 diff: add a config option to control orderfileMichael S. Tsirkin, Apr 23, 2014
  2. 2/6 test: add test_write_lines helperMichael S. Tsirkin, Apr 23, 2014
  3. Junio C HamanoApr 23, 2014
  4. Michael S. TsirkinApr 23, 2014
  5. 3/6 tests: new test for orderfile optionsMichael S. Tsirkin, Apr 23, 2014
  6. Junio C HamanoApr 23, 2014
  7. Michael S. TsirkinApr 23, 2014
  8. 4/6 patch-id: make it stable against hunk reorderingMichael S. Tsirkin, Apr 23, 2014
  9. Junio C HamanoApr 23, 2014
  10. Michael S. TsirkinApr 23, 2014
  11. Junio C HamanoApr 23, 2014
  12. Michael S. TsirkinApr 24, 2014
  13. Junio C HamanoApr 24, 2014
  14. 5/6 patch-id: document new behaviourMichael S. Tsirkin, Apr 23, 2014
  15. 6/6 patch-id-test: test stable and unstable behaviourMichael S. Tsirkin, Apr 23, 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.