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

Re: [PATCH 0/3] t3404 incremental improvements

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Aug 22, 2013, 18:17 UTC
Message-ID
<CAPig+cRM_j7KOKG+YS1aTqz7suDY5LC7kh5-oP5H-GAenUqq-w@mail.gmail.com>
In-Reply-To
<xmqqk3jesk2a.fsf@gitster.dls.corp.google.com>
On Wed, Aug 21, 2013 at 7:25 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> Eric Sunshine <sunshine@sunshineco.com> writes:
>
>> This set of patches was meant to be a re-roll of [1] addressing Junio's
>> comments, however [1] graduated to 'next' before I found time to work on
>> it further, so these are instead incremental patches atop 'next'.
>
> Just FYI, 'next' will be rewound once the upcoming release is done,
> so we have a chance to rewind and squash.

How would we go about this? Is there something I can do to streamline the squashing?

Unfortunately, the various fix-up patches do not have a one-to-one correspondence to the original three patches in 'next'.

Previous: Junio C HamanoNext: Junio C Hamano
Message 11 of 12 in “t3404 incremental improvements”
  1. 0/3 t3404 incremental improvementsEric Sunshine, Aug 21, 2013
  2. 1/3 t3404: preserve test_tick state across short SHA-1 collision testEric Sunshine, Aug 21, 2013
  3. Jonathan NiederAug 25, 2013
  4. Eric SunshineAug 25, 2013
  5. Jonathan NiederAug 25, 2013
  6. Junio C HamanoAug 26, 2013
  7. 2/3 t3404: make tests more self-containedEric Sunshine, Aug 21, 2013
  8. Junio C HamanoAug 21, 2013
  9. 3/3 t3404: simplify short SHA-1 collision testEric Sunshine, Aug 21, 2013
  10. Junio C HamanoAug 21, 2013
  11. Eric SunshineAug 22, 2013
  12. Junio C HamanoAug 22, 2013

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.