From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: master testing time, a possible 9.1.1, and where we stand
Date: Mon, 8 Apr 2013 23:03:22 +0200 [thread overview]
Message-ID: <CAHmME9p9MuNvpNDEVnW8OoKm98mabypG-+J+1-ZiGY+6FX+LSA@mail.gmail.com> (raw)
Hi all,
There's been crazy amounts of churn in the last weeks, and after
reviewing everything, I've merged quite a bit to master. Great work to
everyone who's been sending patches -- John and Lukas in particular.
Things should be pretty stable, but it's also possible we screwed
something up. On the table since the last big merge to master we have
--
- Git's testing framework
- Constness fixes
- Git's makefile
- Git's strbuf
- Git 1.8 series
- Quite a bit of refactoring from Lukas
I'm tempting to also push a 9.1.1 out the door before we start merging
new features, as this has been pretty hectic, and I still have my TODO
list of things I'd like to get done for 9.2. Going forward, expect
more frequent releases when we have this kind of activity.
In any case, we now have some new sensitive code in master, so let's
see what we broke.
As of writing, our current feature branches that may be merged soon
are jd/branch-sort, for kernel.org's branch sorting feature, and
jk/valgrind-tests, with John's wrapper for valgrind.
Jason
reply other threads:[~2013-04-08 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHmME9p9MuNvpNDEVnW8OoKm98mabypG-+J+1-ZiGY+6FX+LSA@mail.gmail.com \
--to=cgit@lists.zx2c4.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).