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

Re: [PATCH] notes: accept any ref for merge

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 22, 2014, 17:34 UTC
Message-ID
<xmqqsijjlfsy.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CALKQrgd3PzwgxuhrTpNCi-zuOj3PYviknpKgfPYVWP6bNS8AqQ@mail.gmail.com>
Johan Herland <johan@herland.net> writes:
Show 7 quoted lines
>> Assuming that this is we all agree to go in that direction, let's
>> make a list of things to be done to codify it, and do them.  For a
>> starter, I think these are needed, perhaps?
>> ...
> Sounds good to me. At least that would ...
> ...
> In addition to that we might want to consider ...

Yes, I specifically meant my list as "a starter", not wanting to make an exhaustive list myself.

Previous: Johan HerlandNext: Kyle J. McKay
Message 6 of 9 in “notes: accept any ref for merge”
  1. notes: accept any ref for mergeScott Chacon, Sep 19, 2014
  2. Jeff KingSep 19, 2014
  3. Johan HerlandSep 19, 2014
  4. Junio C HamanoSep 19, 2014
  5. Johan HerlandSep 20, 2014
  6. Junio C HamanoSep 22, 2014
  7. Kyle J. McKayNov 22, 2014
  8. Jeff KingDec 4, 2014
  9. Junio C HamanoSep 19, 2014

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.