From: Benjamin Siegmund <rialgar42@gmail.com>
To: git@vger.kernel.org
Subject: Help improving the future of debugging
Date: Mon, 25 Aug 2014 17:30:02 +0200 [thread overview]
Message-ID: <CADkk7MOAMrogJ2OUPfzpwJ6g1vTNNhT5ZaZZAa6X5mq3ser-oA@mail.gmail.com> (raw)
Dear Git Developers,
since 1974 researchers and software developers try to ease software
debugging. Over the last years, they created many new tools and
formalized methods. We are interested if these advancements have
reached professional software developers and how they influenced their
approach. To find this out, we are conducting an Online Survey for
Software Developers. From the results we expect new insights into
debugging practice that help us to suggest new directions for future
research. So if you are a software developer or know any software
developers, you can really help us. The survey is, of course, fully
anonymous and will take about 15 minutes to fill out. Feel free to
redistribute this message to anyone who you think might be interested.
The survey can be reached at:
http://www.uni-potsdam.de/skopie-up/index.php/689349
Thank you for your interest,
Benjamin Siegmund
reply other threads:[~2014-08-25 15:30 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=CADkk7MOAMrogJ2OUPfzpwJ6g1vTNNhT5ZaZZAa6X5mq3ser-oA@mail.gmail.com \
--to=rialgar42@gmail.com \
--cc=git@vger.kernel.org \
/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).