public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] CHANGELOG
Date: Fri, 25 May 2007 19:10:58 +0200	[thread overview]
Message-ID: <200705251910.58224.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4656DED3.70706@gmx.net>


Hi,


> hi marek, i see that the rev is updated often, so perhaps it would be
> very useful to write a changelog file with only a content like: 'if you
> wanna see changelog, pleas visit:
> https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/'
>
> as i see the most important changes are listed there, so everyone would
> know where - nobody would ask for anymore. perhaps!

may be even better: What if the script which generates the packages after each 
commit would print the commit history into the CHANGELOG file ?


> oh, sorry i was thinking that you are informed already!

Unfortunately not.  ;-)


> well since rv360, batman is running (well, flying!) here with
> 'batmand -d 1 -p 105.131.41.5 -r 1 eth2', plus 'batmand -c -d 2' in
> another terminal for about 15 hours a day. it stopped working 2 times
> but it was not a segfault and i was able to restart next moment!
> as i installed today rv371, it is running as well as 360, i ll see if it
> will stop sometimes!

Sounds good. Keep us informed.

Regards,
Marek

  reply	other threads:[~2007-05-25 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 11:56 [B.A.T.M.A.N.] CHANGELOG Dragan Noveski
2007-05-25 12:27 ` Axel Neumann
2007-05-25 12:31   ` Dragan Noveski
2007-05-25 12:42 ` Marek Lindner
2007-05-25 13:04   ` Dragan Noveski
2007-05-25 17:10     ` Marek Lindner [this message]
2007-05-26 13:08       ` Dragan Noveski
2007-05-26 13:56         ` Axel Neumann

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=200705251910.58224.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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