From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2015, #03; Mon, 17)
Date: Mon, 17 Aug 2015 16:38:32 -0700 [thread overview]
Message-ID: <xmqq7fotbi4n.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAGZ79ka6mz=f=g0mkgtP2955z+sRf1Sh+ArB=-ZA2ZhX27LuWw@mail.gmail.com> (Stefan Beller's message of "Mon, 17 Aug 2015 16:28:39 -0700")
Stefan Beller <sbeller@google.com> writes:
>> * sb/remove-get-pathspec (2015-08-03) 1 commit
>> - builtin/mv: remove get_pathspec()
>>
>> Expecting a reroll.
>> ($gmane/275224)
>
> IIRC the discussion turned out to expect a
> full conversion of internal_copy_pathspec in builtin/mv
> and not just moving all the cruft there, such that we can
> make the deprecated function non public and update the
> documentation.
>
> So I am not going to spend more time on that series,
OK, then will discard.
>> * jk/git-path (2015-08-10) 16 commits
>> (merged to 'next' on 2015-08-12 at 7ebe864)
>> + memoize common git-path "constant" files
>> + get_repo_path: refactor path-allocation
>> + find_hook: keep our own static buffer
>> + refs.c: remove_empty_directories can take a strbuf
>> + refs.c: avoid git_path assignment in lock_ref_sha1_basic
>> + refs.c: avoid repeated git_path calls in rename_tmp_log
>> + refs.c: simplify strbufs in reflog setup and writing
>> + path.c: drop git_path_submodule
>
> Oops, I just wanted to add a caller to git_path_submodule. I'll also look into
> this series to see the alternatives. :)
I know.
As you may be already aware by observing the tip of 'pu', I have
been queuing evil-merge resolutions to prepare your series for the
world without git_path_submodule(), so "looking into to see
alternatives" shouldn't be too huge a task ;-).
prev parent reply other threads:[~2015-08-17 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 22:34 What's cooking in git.git (Aug 2015, #03; Mon, 17) Junio C Hamano
2015-08-17 23:28 ` Stefan Beller
2015-08-17 23:38 ` Junio C Hamano [this message]
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=xmqq7fotbi4n.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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.