From: Fredrik Kuivinen <frekui@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Makefile: Track changes to LDFLAGS and relink when necessary
Date: Wed, 22 Jun 2011 12:44:05 +0200 [thread overview]
Message-ID: <BANLkTi=4Pj0bLswUNLXebkVOqLOiq2eNoA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=XOEFyVu-ZEqpmLaD60FL6dV2ndA@mail.gmail.com>
On Wed, Jun 22, 2011 at 10:51, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> On Tue, Jun 21, 2011 at 20:58, Fredrik Kuivinen <frekui@gmail.com> wrote:
>
> It might be interesting to note in the commit message why this change
> is made (now), and if there are any other similar flags that we ought
> to track.
I agree, will send an updated patch in a minute. I don't know why the
change hasn't been done before. Maybe people don't change LDFLAGS
that often so it has simply been no need for the change.
- Fredrik
prev parent reply other threads:[~2011-06-22 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 18:58 [PATCH] Makefile: Track changes to LDFLAGS and relink when necessary Fredrik Kuivinen
2011-06-22 8:51 ` Sverre Rabbelier
2011-06-22 10:44 ` Fredrik Kuivinen [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='BANLkTi=4Pj0bLswUNLXebkVOqLOiq2eNoA@mail.gmail.com' \
--to=frekui@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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).