Hi Ian, I didn't think this even got out. I was getting a weird error from git-send-mail when it tried to send to the gmail server and I got distracted with other things.
Here's log: Send this email? ([y]es|[n]o|[q]uit|[a]ll): y Password for 'smtp://[email protected]@smtp.gmail.com:587': OK. Log says: Server: smtp.gmail.com MAIL FROM:<[email protected]> RCPT TO:<[email protected]> From: Courtney Goeltzenleuchter <[email protected]> To: [email protected] Subject: [PATCH] mesa: add bounds checking to eliminate buffer overrun Date: Mon, 7 Apr 2014 13:19:17 -0600 Message-Id: <[email protected]> X-Mailer: git-send-email 1.8.3.2 In-Reply-To: <CAE=6oPATsHZb3ZBH2HVD978tr= [email protected]> References: <CAE=6oPATsHZb3ZBH2HVD978tr= [email protected]> Result: 250 2.0.0 OK 1396898380 on9sm125685igb.11 - gsmtp In git 1.7.0, the default has changed to --no-chain-reply-to Set sendemail.chainreplyto configuration variable to true if you want to keep --chain-reply-to as your default. (mbox) Adding cc: Courtney Goeltzenleuchter <[email protected]> from line 'From: Courtney Goeltzenleuchter <[email protected]>' (body) Adding cc: "9.2 10.0 10.1" <[email protected] from line 'Cc: "9.2 10.0 10.1" <[email protected]' error: unable to extract a valid address from: "9.2 10.0 10.1" < [email protected] What to do with this address? ([q]uit|[d]rop|[e]dit): Looks like git-send-email is interpreting the commit message and trying to add as a cc the last line: Cc: "9.2 10.0 10.1" < [email protected] <mailto:[email protected]>> I'll give it another try. On Mon, Apr 7, 2014 at 2:06 PM, Ian Romanick <[email protected]> wrote: > On 04/07/2014 12:19 PM, Courtney Goeltzenleuchter wrote: > > Updated patch to include reference to bug that it resolves. > > Where? > > The proper way to do this is to send the path with git-send-mail, and > include extra verbage in the commit message like: > > v3: Updated patch to include reference to bug that it resolves. > > Unless, of course, that update is just to add a Bugzilla: line to the > commit message. I don't know if that's the change because... :) > > > Since this fixes a buffer overrun in the driver (found running > GLBenchmark's Manhattan test) I think it would be a good candidate for the > stable branch. > > > > _______________________________________________ > > mesa-dev mailing list > > [email protected] > > http://lists.freedesktop.org/mailman/listinfo/mesa-dev > > -- Courtney Goeltzenleuchter LunarG
_______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
