From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <email@example.com>
Subject: Re: What's cooking in git.git (Nov 2017, #08; Tue, 28)
Date: Fri, 1 Dec 2017 14:33:30 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.22.214.171.1242011431520.98586@virtualbox> (raw)
On Wed, 29 Nov 2017, Junio C Hamano wrote:
> * tz/complete-branch-copy (2017-11-17) 1 commit
> (merged to 'next' on 2017-11-20 at 6d22384fcd)
> + completion: add '--copy' option to 'git branch'
> Command line completion (in contrib/) has been taught about the
> "--copy" option of "git branch".
> * tz/notes-error-to-stderr (2017-11-15) 1 commit
> (merged to 'next' on 2017-11-20 at a45d441ee2)
> + notes: send "Automatic notes merge failed" messages to stderr
> "git notes" sent its error message to its standard output stream,
> which was corrected.
> * tz/redirect-fix (2017-11-14) 2 commits
> (merged to 'next' on 2017-11-20 at 5b13f7026e)
> + rebase: fix stderr redirect in apply_autostash()
> + t/lib-gpg: fix gpgconf stderr redirect to /dev/null
> A few scripts (both in production and tests) incorrectly redirected
> their error output. These have been corrected.
I guess I am the only one, but I have to say: I get confused *constantly*
when you mention Todd's patches in the "What's cooking" mails, always
expecting something timezone-related to be going on.
P.S.: You mentioned that you'd go offline today, should I hold off with
more of Git for Windows' upstreaming? If so, how long?
next prev parent reply other threads:[~2017-12-01 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 1:17 What's cooking in git.git (Nov 2017, #08; Tue, 28) Junio C Hamano
2017-12-01 13:33 ` Johannes Schindelin [this message]
2017-12-01 13:38 ` cc/require-tcl-tk-for-build, was " Johannes Schindelin
2017-12-01 13:49 ` jt/diff-anchored-patience, " Johannes Schindelin
2017-12-01 13:56 ` Lars Schneider
2017-12-01 14:32 ` jn/reproducible-build, was " Johannes Schindelin
2017-12-01 15:41 ` Lars Schneider
2017-12-01 16:49 ` Jeff Hostetler
2017-12-03 0:27 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).