From: Matthew Hall <mhall-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
To: Thomas Monjalon
<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: rc1 / call for review
Date: Mon, 29 Sep 2014 22:29:41 -0700 [thread overview]
Message-ID: <20140930052941.GA1834@mhcomputing.net> (raw)
In-Reply-To: <1600627.I6ZYUK1NqR@xps13>
On Tue, Sep 30, 2014 at 06:52:45AM +0200, Thomas Monjalon wrote:
> You're right.
> During integration time, app hackers should be able to check the git history
> for these API changes.
> When it will be officially released, there will be some notes in the
> documentation to help porting applications.
It works for commercial apps where we have 40 hrs / week to look. But for my
open source app I guess I just have to do step 1) compile, step 2) pray that
it still works. ;)
Matthew.
prev parent reply other threads:[~2014-09-30 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 20:23 rc1 / call for review Thomas Monjalon
2014-09-29 21:33 ` Matthew Hall
[not found] ` <20140929213341.GA589-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2014-09-30 4:52 ` Thomas Monjalon
2014-09-30 5:29 ` Matthew Hall [this message]
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=20140930052941.GA1834@mhcomputing.net \
--to=mhall-hv3ognyu3jfzzajbqzqcxq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.