b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: "Stephan Enderlein (Freifunk Dresden)" <freifunk@ddmesh.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
Subject: Re: [B.A.T.M.A.N.] My patches don't reference you mails
Date: Fri, 26 Sep 2008 14:56:17 +0200 (CEST)	[thread overview]
Message-ID: <05adc8043fec923c9bc119c50e24501e.squirrel@wm.ddmesh.de> (raw)
In-Reply-To: <200809261419.28752.sven.eckelmann@gmx.de>


>   https://list.open-mesh.net/pipermail/b.a.t.m.a.n/2008-September.txt.gz
If I look at this file I agree with you that there is no In-Replay-To.
But the email header is normaly much longer. So we can see this if you
create a new message for the list (not a reply).
The mailing list modifies the emails and removes a lot of header entries.

Perhaps the mailing list has a problem with multi-part email. Have you
tried to send new emails without attachments/pgp?
If it is working than the mailing ist has a problem with that and
attachments should be avoided.

Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url :
From sven.eckelmann at gmx.de  Fri Sep 12 16:59:45 2008


Dipl.Informatiker(FH) Stephan Enderlein
Freifunk Dresden

  reply	other threads:[~2008-09-26 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 21:59 [B.A.T.M.A.N.] [PATCH] Send TUNNEL_IP_REQUEST as response of TUNNEL_IP_REQUEST Sven Eckelmann
2008-09-25  9:12 ` Stephan Enderlein (Freifunk Dresden)
2008-09-25  9:33   ` Sven Eckelmann
2008-09-26 11:19     ` Stephan Enderlein (Freifunk Dresden)
2008-09-26 11:39       ` Sven Eckelmann
2008-09-26 12:19         ` [B.A.T.M.A.N.] My patches don't reference you mails Sven Eckelmann
2008-09-26 12:56           ` Stephan Enderlein (Freifunk Dresden) [this message]
2008-09-26 13:06             ` Sven Eckelmann
2008-09-26 15:49               ` Marek Lindner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=05adc8043fec923c9bc119c50e24501e.squirrel@wm.ddmesh.de \
    --to=freifunk@ddmesh.de \
    --cc=b.a.t.m.a.n@open-mesh.net \


* 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).