From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2017, #03; Wed, 8)
Date: Wed, 8 Nov 2017 10:09:33 -0800 [thread overview]
Message-ID: <20171108180933.GA11916@google.com> (raw)
In-Reply-To: <xmqqinell3of.fsf@gitster.mtv.corp.google.com>
On 11/08, Junio C Hamano wrote:
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'. The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
>
> The tip of 'next' has been rebuilt on top of v2.15, while kicking a
> few topics back to 'pu'.
>
> You can find the changes described here in the integration branches
> of the repositories listed at
>
> http://git-blame.blogspot.com/p/git-public-repositories.html
>
> --------------------------------------------------
> [New Topics]
>
> * bw/rebase-i-ignored-submodule-fix (2017-11-07) 1 commit
> - wt-status: actually ignore submodules when requested
>
> "git rebase -i" recently started misbehaving when a submodule that
> is configured with 'submodule.<name>.ignore' is dirty; this has
> been corrected.
>
> Will merge to 'next'.
> I've edited in the tweak brought up in the discussion. Please
> eyeball to sanity check.
Tweaks look good to me!
--
Brandon Williams
next prev parent reply other threads:[~2017-11-08 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 5:50 What's cooking in git.git (Nov 2017, #03; Wed, 8) Junio C Hamano
2017-11-08 18:09 ` Brandon Williams [this message]
2017-11-11 0:32 ` brian m. carlson
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=20171108180933.GA11916@google.com \
--to=bmwill@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).