From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Newbie task: Fix a build regression
Date: Mon, 02 Jun 2014 15:06:50 -0400 [thread overview]
Message-ID: <29840.1401736010@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 02 Jun 2014 20:56:35 +0200." <CAFLxGvyc14G5jQ+aM8kazEt3jFBqdJgrvZ0N=Y3kGtcVdgG=Rw@mail.gmail.com>
On Mon, 02 Jun 2014 20:56:35 +0200, Richard Weinberger said:
> 1. Find out which commit broke the build (i.e. using git bisect)
Any hint on a starting value for 'git bisect good v3.mumble'? :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140602/f13d5651/attachment.bin
next prev parent reply other threads:[~2014-06-02 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 18:56 Newbie task: Fix a build regression Richard Weinberger
2014-06-02 19:06 ` Valdis.Kletnieks at vt.edu [this message]
2014-06-02 19:10 ` Richard Weinberger
2014-06-02 19:19 ` Valdis.Kletnieks at vt.edu
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=29840.1401736010@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).