From: Christian Couder <chriscool@tuxfamily.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Avery Pennarun <apenwarr@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Andreas Ericsson <ae@op5.se>
Subject: Input welcome for "Git Bisect and Testing" presentation at GTAC 2010
Date: Sun, 12 Sep 2010 22:25:52 +0200 [thread overview]
Message-ID: <201009122225.52520.chriscool@tuxfamily.org> (raw)
Hi,
The Google Test Automation Conference (http://www.gtac.biz) committee accepted
my proposal for a "Git Bisect and Testing" presentation at the GTAC 2010 in
India on October 28 and 29. So I am working on it.
It will be roughly based on my previous "Fighting regressions with git bisect"
article (http://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html)
and presentation (http://www.linux-kongress.org/2009/slides/fighting_regressions_with_git_bisect_christian_couder.pdf).
But I would be happy to add more concrete examples of how "git bisect" is used
in the real world. And more generally I am very open to any kind of feedback
about "git bisect".
For example it can be how "git bisect run" is used automatically in build
systems, or how "git bisect" is used manually on GUI applications in your
company, or how you use Avery Pennarun's "git-builder" (http://github.com/apenwarr/gitbuilder, it uses "git bisect"
underneath), or what features you would want to see added, or what have been
your experience with it, and so on.
Thanks in advance,
Christian.
PS: Because of this presentation I won't come to the GitTogether this year.
Anyway I wish people going there an happy GitTogether'10!
next reply other threads:[~2010-09-12 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 20:25 Christian Couder [this message]
2010-09-13 8:04 ` Input welcome for "Git Bisect and Testing" presentation at GTAC 2010 Avery Pennarun
2010-09-13 19:37 ` Christian Couder
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=201009122225.52520.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=ae@op5.se \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mingo@elte.hu \
/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).