From: Sven Eckelmann <sven@narfation.org>
To: Michael Tautschnig <mt@debian.org>
Cc: 703540@bugs.debian.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Bug#703540: Inconsistent use of _GNU_SOURCE
Date: Tue, 02 Apr 2013 11:10:37 +0200 [thread overview]
Message-ID: <6694164.toG189sgU4@bentobox> (raw)
In-Reply-To: <20130329114816.GR798@l04.local>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Friday 29 March 2013 11:48:16 Michael Tautschnig wrote:
> Hi Sven, hi all,
>
> [...]
>
> > > Either all or no file should #define _GNU_SOURCE.
> >
> > Please add information how to reproduce this the next time you are adding
> > such such a bug. Now I can just assume what you are writing is true (even
> > when the man page about sendto says otherwise).
[...]
> Just one question before I elaborate a bit: what information in the man page
> are you referring to? I can't quite seem to see anything mentioning
> _GNU_SOURCE?
Yes, this was exactly the thing I was pointing out:
> > > (This was at least noticed for the sendto function, but may extend to
> > > others.)
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-02 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130320175154.GT41481@l04.local>
2013-03-21 8:24 ` [B.A.T.M.A.N.] Bug#703540: Inconsistent use of _GNU_SOURCE Sven Eckelmann
2013-03-21 15:16 ` [B.A.T.M.A.N.] [PATCH] batmand: Either all or no source file should #define _GNU_SOURCE Elektra
2013-03-21 15:20 ` Elektra
2013-03-29 11:48 ` [B.A.T.M.A.N.] Bug#703540: Inconsistent use of _GNU_SOURCE Michael Tautschnig
2013-03-29 12:37 ` Antonio Quartulli
2013-04-02 9:10 ` Sven Eckelmann [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=6694164.toG189sgU4@bentobox \
--to=sven@narfation.org \
--cc=703540@bugs.debian.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mt@debian.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.