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

Re: [PATCH 1/3] trailer: add a trailer.trimEmpty config option

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 9, 2015, 18:23 UTC
Message-ID
<xmqqy4o7aqqi.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAP8UFD1pWH5yaJaJ_gV1t5q5qfgs58AtcSr+ZqDTnWzfHK1uBw@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 6 quoted lines
> It is not designed like this because you only asked me to design it
> like this after the facts, when there was another email thread about
> conflicts blocks and one function you created could be used by the
> trailer code too.
>
> If you had asked this from the beginning I would certainly have done...

Because the process here is not somebody outlines the design and gives it to laborer to implement, "after the fact" and "from the beginning" are complaining to and asking for impossible. You design and implement and then it gets reviewed, not the other way around.

Previous: Christian CouderNext: Junio C Hamano
Message 4 of 6 in “trailer: add a trailer.trimEmpty config option”
  1. 1/3 trailer: add a trailer.trimEmpty config optionChristian Couder, Feb 7, 2015
  2. Junio C HamanoFeb 7, 2015
  3. Christian CouderFeb 7, 2015
  4. Junio C HamanoFeb 9, 2015
  5. Junio C HamanoFeb 10, 2015
  6. Junio C HamanoFeb 10, 2015

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.