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

Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)

From
Heba Waly <heba.waly@gmail.com>
Date
Mar 5, 2020, 15:17 UTC
Message-ID
<CACg5j26uLyyHRx0ouVhUbJ8P20uJgvN4WCqunP5OoXhGyxuadA@mail.gmail.com>
In-Reply-To
<xmqqpnds5c1v.fsf@gitster-ct.c.googlers.com>
On Thu, Mar 5, 2020 at 5:18 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 23 quoted lines
>
> Heba Waly <heba.waly@gmail.com> writes:
>
> >> * hw/advise-ng (2020-03-02) 5 commits
> >>  - tag: use new advice API to check visibility
> >>  - SQUASH???
> >
> > A local change that needs to be squashed?
>
> I often leave these changes that are based on what I suggested in my
> review (or what somebody else suggested and I found sensible) as a
> separate "SQUASH???" patch while queuing, when I can foresee myself
> changing minds later (on the other hand, trivial typofixes etc. are
> often squashed directly into the patches as I queue), so that these
> can be removed easily.
>
> As such, if the original author agrees with the suggestion, it is OK
> to include it in the next round (when the suggested change is small
> enough, don't bother with "Helped-by").  It is OK to drop it from
> the next round when the original author does not agree with the
> suggestion, too, but it would be good to say why somewhere in the
> discussion.
>
Got it, thanks Junio and Jonathan for your replies.
Heba
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 15 in “What's cooking in git.git (Mar 2020, #01; Tue, 3)”
  1. Junio C HamanoMar 3, 2020
  2. Taylor BlauMar 3, 2020
  3. Junio C HamanoMar 3, 2020
  4. Junio C HamanoMar 3, 2020
  5. Taylor BlauMar 3, 2020
  6. Heba WalyMar 4, 2020
  7. Jonathan TanMar 4, 2020
  8. Junio C HamanoMar 4, 2020
  9. Heba WalyMar 5, 2020
  10. update how-to-maintain-gitJunio C Hamano, Mar 6, 2020
  11. Eric SunshineMar 6, 2020
  12. Junio C HamanoMar 6, 2020
  13. Martin ÅgrenMar 7, 2020
  14. hv/receive-denycurrent-everywhere, was Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)Johannes Schindelin, Mar 4, 2020
  15. Junio C HamanoMar 4, 2020

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.