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

Re: [PATCH 2/2] stash: use "stash--helper"

From
Stefan Beller <sbeller@google.com>
Date
Jan 28, 2016, 21:41 UTC
Message-ID
<CAGZ79kYVRY+6zFnHe8LPp2E_W_gAs--Vog-HoqXW-Do_WgHGXw@mail.gmail.com>
In-Reply-To
<BLU436-SMTP572EDBE67B8D37ECADD616A5DA0@phx.gbl>
On Thu, Jan 28, 2016 at 1:25 PM, Matthias Aßhauer <mha1993@live.de> wrote:
>> You had some good measurements in the coverletter, which is not going to be recorded in the projects history. This part however would be part of the commit.
>> So you could move the speed improvements here (as well as the other reasoning) on why this is a good idea. :)
>
> I considered that, but I thought it would inflate the size of the commit message quite a bit and represents a  pretty temporary information as I'm planning to port more code.

No worries about too large commit messages. ;) See dcd1742e56ebb944c4ff62346da4548e1e3be675 as an example for commit message per code raio what Jeff usually produces. :)

> Any further progression on this would make the old meassurements kind of obsolete IMHO.

Well it records that this specific step was beneficial, too, on the platforms you measured on. If it turns out to there is a regression after you rewrote lots of code, it is still traceable that this commit was done in good faith.

> I decided to move it to the coverletter, because it is only valid information if you consider both commits. If the general opinion on here is that I should add it to the commit message though, I'll gladly update it.

Heh, true. However you enable the speedup in the second patch. If you were to apply only the first (add the helper), you'd not see the difference, so maybe it's worth adding it to the second commit message.

Show 6 quoted lines
>
>>> https://github.com/git/git/pull/191
>>
>> Oh I see you're using the pull-request to email translator, cool!
>
> Yes, I did. It definitly makes things easier if you are not used to mailing lists, but it was also a bit of a kerfuffle. I tried to start working on coverletter support, but I couldn't get it to accept the amazon SES credentials I provided. I ended up manually submiting the coverletter. It also didn't like my name.

Not sure if Roberto, the creator of that tool, follows the mailing list. I cc'd him.

>
> Thank you for your quick feedback.
>
Previous: Matthias AßhauerNext: Roberto Tyley
Message 5 of 14 in “stash--helper: implement "git stash--helper"”
  1. 1/2 stash--helper: implement "git stash--helper"Matthias Asshauer, Jan 28, 2016
  2. 2/2 stash: use "stash--helper"Matthias Asshauer, Jan 28, 2016
  3. Stefan BellerJan 28, 2016
  4. AW: [PATCH 2/2] stash: use "stash--helper"Matthias Aßhauer, Jan 28, 2016
  5. Stefan BellerJan 28, 2016
  6. Roberto TyleyJan 28, 2016
  7. AW: [PATCH 2/2] stash: use "stash--helper"Matthias Aßhauer, Jan 29, 2016
  8. Thomas GummererJan 29, 2016
  9. Junio C HamanoJan 29, 2016
  10. Junio C HamanoJan 28, 2016
  11. AW: [PATCH 1/2] stash--helper: implement "git stash--helper"Matthias Aßhauer, Jan 29, 2016
  12. Junio C HamanoJan 29, 2016
  13. Michael BlumeFeb 1, 2016
  14. Junio C HamanoFeb 1, 2016

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.