b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
Subject: [B.A.T.M.A.N.] My patches don't reference you mails
Date: Fri, 26 Sep 2008 14:19:25 +0200	[thread overview]
Message-ID: <200809261419.28752.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <200809261339.33036.sven.eckelmann@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

On Friday 26 September 2008 13:39:30 Sven Eckelmann wrote:
> On Friday 26 September 2008 13:19:19 Stephan Enderlein (Freifunk Dresden)
> > [...]
> > When I display the complete email header of you emails I have the
> > following line:
> > "In-Reply-To: <6fd627b9bdd448cd88026446baddb8a5.squirrel@wm.ddmesh.de>"
> > For some reason you are creating emails with that header entry instead
> > without it.
> Can you please say which mail you mean? I checked different [PATCH] mails
> from me (send by mailman back to me) and cannot find it. The only ones
> which have them are the the real answers to your mails - which off course
> have references to them.
> grep -rli "6fd627b9bdd448cd88026446baddb8a5.squirrel@wm.ddmesh.de" *|xargs
> grep Subject
> 1222335445.3922.Wd6Iu:2,S:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send
> TUNNEL_IP_REQUEST as response of
> 1222334362.3922.FhPMA:2,RS:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send
> TUNNEL_IP_REQUEST as response of
> 1222428286.3965.lxuDX:Subject: Re: [B.A.T.M.A.N.] [PATCH] Send
> TUNNEL_IP_REQUEST as response o

To have the same data please download
and search for
  Message-ID: <20080924215939.GA9277@sven-desktop.lazhur.ath.cx>
This is the first mail which is displayed as answer to your mail inside the 
threaded archive output. Do you see anything which justifies that this mail is 
attached to your mail in the thread?

Now search for
  Message-ID: <6fd627b9bdd448cd88026446baddb8a5.squirrel@wm.ddmesh.de>
This is the mail you wrote that you think that I "answered" to your mail. Do 
you find the In-Reply-To and References? I do - and this should be the only 
real reason that your mail is a answer to my mail for a mail reader (and for 
the archive output of mailman of course).

Best regards,
	Sven Eckelmann

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-09-26 12:19 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         ` Sven Eckelmann [this message]
2008-09-26 12:56           ` [B.A.T.M.A.N.] My patches don't reference you mails Stephan Enderlein (Freifunk Dresden)
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=200809261419.28752.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.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).