From: greened@obbligato.org (David A. Greene)
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2016, #02; Mon, 11)
Date: Tue, 12 Jan 2016 20:56:41 -0600 [thread overview]
Message-ID: <874meip4pi.fsf@waller.obbligato.org> (raw)
In-Reply-To: <xmqqlh7vvfxc.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 11 Jan 2016 15:45:35 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> * dw/subtree-split-do-not-drop-merge (2015-12-10) 1 commit
> - contrib/subtree: fix "subtree split" skipped-merge bug
>
> The "split" subcommand of "git subtree" (in contrib/) incorrectly
> skipped merges when it shouldn't, which was corrected.
>
> Waiting for review from 'subtree' folks.
Just saw this one now. I'm sorry I missed it. I will go review the
latest version of that.
> * rm/subtree-unwrap-tags (2015-11-24) 1 commit
> - contrib/subtree: unwrap tag refs
>
> Waiting for review from subtree folks.
Looks good. I just sent (very late) follow-up messages.
-David
next prev parent reply other threads:[~2016-01-13 2:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 23:45 What's cooking in git.git (Jan 2016, #02; Mon, 11) Junio C Hamano
2016-01-12 0:06 ` Mike Hommey
2016-01-12 3:04 ` Junio C Hamano
2016-01-12 4:34 ` Edmundo Carmona Antoranz
2016-01-12 8:39 ` Johannes Schindelin
2016-01-12 18:47 ` Junio C Hamano
2016-01-12 21:49 ` Jeff King
2016-01-13 23:07 ` Junio C Hamano
2016-01-13 23:22 ` Jeff King
2016-01-13 23:44 ` Junio C Hamano
2016-01-13 23:54 ` Junio C Hamano
2016-01-14 10:21 ` Jeff King
2016-01-13 2:56 ` David A. Greene [this message]
2016-01-18 13:35 ` Michael J Gruber
2016-01-18 17:06 ` Jeff King
2016-01-18 21:39 ` Eric Wong
2016-01-19 7:07 ` Michael J Gruber
2016-01-25 9:56 ` Duy Nguyen
2016-01-25 22:03 ` 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=874meip4pi.fsf@waller.obbligato.org \
--to=greened@obbligato.org \
--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.