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

Re: What's cooking in git.git (Oct 2011, #04; Wed, 12)

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 13, 2011, 06:02 UTC
Message-ID
<m3zkh577ln.fsf@localhost.localdomain>
In-Reply-To
<7vipnu9hbj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 7 quoted lines
> * cs/perl-config-path-send-email (2011-09-30) 2 commits
>   (merged to 'next' on 2011-10-06 at 93c00f0)
>  + use new Git::config_path() for aliasesfile
>  + Add Git::config_path()
> 
> Originally merged to 'next' on 2011-10-05.
> Will merge to 'master' in the second wave.
What about
   . Refactor Git::config_*
from
   [PATCH/RFC 3/2] Refactor Git::config_*
   http://thread.gmane.org/gmane.comp.version-control.git/182310/focus=183111
Ahhh... sorry, it is marked as an RFC.  Should I resend?
-- 
Jakub Narębski
Previous: Junio C HamanoNext: Brad King
Message 4 of 8 in “What's cooking in git.git (Oct 2011, #04; Wed, 12)”
  1. Junio C HamanoOct 12, 2011
  2. Jeff KingOct 12, 2011
  3. Junio C HamanoOct 12, 2011
  4. Jakub NarebskiOct 13, 2011
  5. 0/2 Do not search submodules in deep recursive mergeBrad King, Oct 13, 2011
  6. 1/2 submodule: Demonstrate known breakage during recursive mergeBrad King, Oct 13, 2011
  7. 2/2 submodule: Search for merges only at end of recursive mergeBrad King, Oct 13, 2011
  8. Junio C HamanoOct 13, 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.