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

Re: What's cooking in git.git (Aug 2011, #03; Thu, 11)

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 18, 2011, 17:30 UTC
Message-ID
<CALkWK0mN_SUK4pkZZccmvTTrAJK0ZPjY77d7iaKT8RWtEJzFCg@mail.gmail.com>
In-Reply-To
<7vwredi9uu.fsf@alter.siamese.dyndns.org>
Hi Junio,
Junio C Hamano writes:
Show 11 quoted lines
> Ramkumar Ramachandra <artagnon@gmail.com> writes:
>>> * rr/revert-cherry-pick-continue (2011-08-08) 18 commits
>>> [...]
>>> Will merge to "next".
>>
>> If this won't graduate to 'next' before the 24th, I have plenty of
>> time to re-roll fixing all the issues that I've addressed in the
>> beginning of the new series.
>
> I take it that you mean by "the new series" the 6-patch "Towards a
> generalized sequencer" topic?
Yes.
Show 5 quoted lines
> It is ultimately up-to-you. If you feel the fix-up is against glaring
> errors in the earlier round that you would prefer not to see in the
> history cast-in-stone, I am perfectly Ok to wait for a re-roll. On the
> other hand, if they are mostly cosmetic fixes without major semantic
> changes, it may be easier for everybody to see them fixed in-tree.

Hm, I didn't think they were glaring errors. After reading your latest review about my '--continue' patch in the generalized sequencer, I've decided not to re-roll. Please merge 'rr/revert-cherry-pick-continue' into 'next' as usual. It'll take me some more time to think about my "generalized sequencer" series.

Thanks.
-- Ram
Previous: Junio C HamanoNext: Pascal Obry
Message 6 of 12 in “What's cooking in git.git (Aug 2011, #03; Thu, 11)”
  1. Junio C HamanoAug 11, 2011
  2. Philip OakleyAug 13, 2011
  3. Junio C HamanoAug 16, 2011
  4. Ramkumar RamachandraAug 14, 2011
  5. Junio C HamanoAug 16, 2011
  6. Ramkumar RamachandraAug 18, 2011
  7. Pascal ObryAug 18, 2011
  8. Junio C HamanoAug 18, 2011
  9. Ramsay JonesAug 20, 2011
  10. Junio C HamanoAug 23, 2011
  11. Johannes SixtAug 24, 2011
  12. Pascal ObryAug 21, 2011

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.