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

Re: [PATCH v6 0/3] rr/fmt-merge-msg replacement

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 26, 2010, 16:58 UTC
Message-ID
<7v7hjdmhtn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100826051235.GA9407@kytes>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 7 quoted lines
>> Just as a future reference, in a case like this that results in trivial
>> conflict, I'd prefer to see a patch that can be used independently from
>> other unrelated branches.
>
> Oh, okay. I think I realize why- if the dependent topics are ejected,
> you'll have more trouble taking this forward to `next` and `master`,
> right?

Not just "ejection". In general topics mature at different rates, and there is no point requiring the other unrelated topic to graduate first to 'master' before your topic does.

>> Maybe you'd want a new test or two in t6200?
>
> Good idea! It'll give me the chance to familiarize myself with
> test-lib.sh :)
Previous: Ramkumar Ramachandra
Message 7 of 7 in “rr/fmt-merge-msg replacement”
  1. 0/3 rr/fmt-merge-msg replacementRamkumar Ramachandra, Aug 25, 2010
  2. 1/3 fmt_merge_msg: Change fmt_merge_msg API to accept shortlog_lenRamkumar Ramachandra, Aug 25, 2010
  3. 2/3 merge: Make '--log' an integer option for number of shortlog entriesRamkumar Ramachandra, Aug 25, 2010
  4. 3/3 merge: Make 'merge.log' an integer or boolean optionRamkumar Ramachandra, Aug 25, 2010
  5. Junio C HamanoAug 25, 2010
  6. Ramkumar RamachandraAug 26, 2010
  7. Junio C HamanoAug 26, 2010

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.