From: Junio C Hamano <gitster@pobox•com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
Cc: git@vger•kernel.org, Ben Peart <peartben@gmail•com>,
xiaoqiang zhao <zxq_yx_007@163•com>
Subject: Re: What's cooking in git.git (Jun 2017, #06; Thu, 22)
Date: Thu, 22 Jun 2017 22:28:07 -0700 [thread overview]
Message-ID: <xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <877f03k4tp.fsf@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 23 Jun 2017 00:58:26 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail•com> writes:
> On Thu, Jun 22 2017, Junio C. Hamano jotted:
>
>> * sd/branch-copy (2017-06-18) 3 commits
>> - branch: add a --copy (-c) option to go with --move (-m)
>> - branch: add test for -m renaming multiple config sections
>> - config: create a function to format section headers
>>
>> "git branch" learned "-c/-C" to create and switch to a new branch
>> by copying an existing one.
>>
>> Has a bit of interaction with two other topics, so perhaps needs to
>> wait for them to stabilize a bit more.
>
> What topics are those? Didn't see any outright conflicts, but might have
> missed something. Anything Sahil & I can help with?
Sorry, I write these and then forget the details because I have to
tend to many other topics all the time X-<. Perhaps attempting the
merge to 'pu' yourself will tell you more?
>> * ab/sha1dc (2017-06-07) 2 commits
>> ...
>> Will keep in 'pu'.
>> Impact to the various build and release infrastructure of using
>> submodule is not yet fully known, but this lets us dip our toes.
> ...
> But it's been 1 month kicking around in pu now. What are we gaining from
> keeping it there even longer at this point?
Keeping as many things outside 'next' means I have less things I
have to worry about ;-)
I am sort of waiting for a success from Windows box at Travis. It
hasn't passed for other reasons for a while, though.
>> * xz/send-email-batch-size (2017-05-23) 1 commit
>> - send-email: --batch-size to work around some SMTP server limit
>>
>> "git send-email" learned to overcome some SMTP server limitation
>> that does not allow many pieces of e-mails to be sent over a single
>> session.
>>
>> Waiting for response.
>> cf. <CACBZZX5GYV50rjg9X602JHqFPaoofH9TwDf_-r_MDu8-rmNV6Q@mail•gmail.com>
>
> I think between <7993e188.d18d.15c3560bcaf.Coremail.zxq_yx_007@163•com>
> & <20170523103050.1f7ab7e0@jvn> we have sufficient info about what bug
> this solves to try an alternate approach at some other time.
I thought your wish (which I found reasonable) was to record
whatever information that would help us in the future in the log
message? I was waiting for that to happen.
next prev parent reply other threads:[~2017-06-23 5:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 22:35 What's cooking in git.git (Jun 2017, #06; Thu, 22) Junio C Hamano
2017-06-22 22:58 ` Ævar Arnfjörð Bjarmason
2017-06-23 5:28 ` Junio C Hamano [this message]
2017-06-24 0:27 ` Junio C Hamano
2017-06-23 9:43 ` Lars Schneider
2017-06-23 21:59 ` Ævar Arnfjörð Bjarmason
2017-06-23 23:39 ` Stefan Beller
2017-06-24 0:37 ` Junio C Hamano
2017-06-24 1:01 ` Junio C Hamano
2017-06-27 2:58 ` Stefan Beller
2017-06-24 0:16 ` Stefan Beller
2017-06-24 0:33 ` 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=xmqqo9tfff2w.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peartben@gmail$(echo .)com \
--cc=zxq_yx_007@163$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox