From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2013, #04; Wed, 15)
Date: Wed, 15 May 2013 17:25:52 -0700 [thread overview]
Message-ID: <CAJDDKr5T6rcAukeDkU4niLn7gaz-+JMSE=fG3G4qdKuf-q6AaA@mail.gmail.com> (raw)
In-Reply-To: <7vmwrvajye.fsf@alter.siamese.dyndns.org>
On Wed, May 15, 2013 at 4:42 PM, Junio C Hamano <gitster@pobox.com> 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'.
>
> We are past -rc2 and haven't seen any regression reported since the
> feature freeze started, which may be a good sign (the coming release
> is perfect) or a bad sign (nobody is testing). We'll see soon when
> we tag the 1.8.3 final sometime next week. We may see subsystem
> (git-svn? gitk? git-gui?) and l10n updates before that happens.
>
> 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]
>
> * dw/asciidoc-sources-are-dot-txt-files (2013-05-10) 1 commit
> - CodingGuidelines: Documentation/*.txt are the sources
>
>
> * fc/doc-style (2013-05-09) 2 commits
> - SQUASH??? more consistently update docs
> - documentation: trivial style cleanups
>
>
> * da/darwin (2013-05-15) 3 commits
> - imap-send: eliminate HMAC deprecation warnings on Mac OS X
> - cache.h: eliminate SHA-1 deprecation warnings on Mac OS X
> - Makefile: fix default regex settings on Darwin
>
> Waiting for polishing discussion to finish.
Thanks.
imap-send and cache.h are now on their v6 patch which I just sent.
That last few rounds have been cosmetic/superficial changes and I
would like to consider this topic "done". We've painted this shed
enough times ;-)
I believe "fix default regex settings on Darwin" is uncontroversial
and should be included in the upcoming release. It may even be
maint-worthy. Without it we fail t0070-fundamental.sh. The two
patches that follow it can wait and cook like normal.
--
David
next prev parent reply other threads:[~2013-05-16 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 23:42 What's cooking in git.git (May 2013, #04; Wed, 15) Junio C Hamano
2013-05-16 0:25 ` David Aguilar [this message]
2013-05-20 10:18 ` Duy Nguyen
2013-05-20 16:17 ` Junio C Hamano
2013-05-21 7:13 ` Thomas Rast
2013-05-21 15:27 ` Junio C Hamano
2013-05-27 10:36 ` Duy Nguyen
2013-05-28 21:25 ` Junio C Hamano
2013-05-20 23:08 ` Felipe Contreras
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='CAJDDKr5T6rcAukeDkU4niLn7gaz-+JMSE=fG3G4qdKuf-q6AaA@mail.gmail.com' \
--to=davvid@gmail.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 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.