From: Johannes Sixt <j6t@kdbg.org>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Lars Schneider <larsxschneider@gmail.com>
Subject: Re: 2.11.0-rc1 will not be tagged for a few days
Date: Tue, 8 Nov 2016 07:25:26 +0100 [thread overview]
Message-ID: <65a1bb6d-e924-21aa-70d3-303ebdc499f1@kdbg.org> (raw)
In-Reply-To: <20161108004038.a7gyoe6wpucxjmvz@sigill.intra.peff.net>
Am 08.11.2016 um 01:40 schrieb Jeff King:
> In addition to J6t's fix in t0021, ...
Just to get things straight: Of my two patches, this one ("uniq -c
variations")
https://public-inbox.org/git/c842e0a7-b032-e0c4-0995-f11d93c17c0a@kdbg.org/
is a bug fix in my environment, and I have a suspicion that it is also
required in other less frequently tested environments (Solaris? BSD
variants?)
The other one, which you most likely remember as dealing with "leading
whitespace in wc -c"
https://public-inbox.org/git/b87ddffd-3de1-4481-b484-9f03a73b6ad1@kdbg.org/
is "only" an optimization. The link points at the final version.
-- Hannes
next prev parent reply other threads:[~2016-11-08 6:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:32 2.11.0-rc1 will not be tagged for a few days Junio C Hamano
2016-11-08 0:40 ` Jeff King
2016-11-08 6:25 ` Johannes Sixt [this message]
2016-11-08 21:48 ` Jeff King
2016-11-09 6:29 ` Junio C Hamano
2016-11-09 16:51 ` Jeff King
2016-11-09 23:35 ` Junio C Hamano
2016-11-09 23:40 ` Junio C Hamano
2016-11-10 21:43 ` Junio C Hamano
2016-11-11 0:26 ` Junio C Hamano
2016-11-11 16:13 ` Johannes Schindelin
2016-11-11 17:02 ` Johannes Schindelin
2016-11-11 17:05 ` Lars Schneider
2016-11-11 17:31 ` Lars Schneider
2016-11-11 17:38 ` Lars Schneider
2016-11-11 20:44 ` Johannes Sixt
2016-11-11 20:52 ` Junio C Hamano
2016-11-11 21:07 ` Junio C Hamano
2016-11-11 21:22 ` Johannes Sixt
2016-11-12 13:33 ` Lars Schneider
2016-11-11 17:41 ` 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
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 \
--in-reply-to=65a1bb6d-e924-21aa-70d3-303ebdc499f1@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).