From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Cord Seele <cowose@googlemail.com>,
Cord Seele <cowose@gmail.com>
Subject: Re: What's cooking in git.git (Oct 2011, #04; Wed, 12)
Date: Wed, 12 Oct 2011 23:02:45 -0700 (PDT) [thread overview]
Message-ID: <m3zkh577ln.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vipnu9hbj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * 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
next prev parent reply other threads:[~2011-10-13 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:48 What's cooking in git.git (Oct 2011, #04; Wed, 12) Junio C Hamano
2011-10-12 19:02 ` Jeff King
2011-10-12 19:05 ` Junio C Hamano
2011-10-13 6:02 ` Jakub Narebski [this message]
2011-10-13 12:59 ` [PATCH 0/2] Do not search submodules in deep recursive merge Brad King
2011-10-13 12:59 ` [PATCH 1/2] submodule: Demonstrate known breakage during " Brad King
2011-10-13 12:59 ` [PATCH 2/2] submodule: Search for merges only at end of " Brad King
2011-10-13 18:15 ` [PATCH 0/2] Do not search submodules in deep " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zkh577ln.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=cowose@gmail.com \
--cc=cowose@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.