From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: netdev@vger.kernel.org, lindner_marek@yahoo.de,
David Miller <davem@davemloft.net>
Subject: Re: [B.A.T.M.A.N.] pull request: batman-adv 2012-02-17
Date: Fri, 17 Feb 2012 21:44:19 +0100 [thread overview]
Message-ID: <1990573.JisbTKXt7B@sven-laptop.home.narfation.org> (raw)
In-Reply-To: <20120217.152323.2251437927591117547.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Friday 17 February 2012 15:23:23 David Miller wrote:
> From: Marek Lindner <lindner_marek@yahoo.de>
> Date: Fri, 17 Feb 2012 15:18:20 +0800
>
> > The following changes since commit
dcd6c92267155e70a94b3927bce681ce74b80d1f:
> > Linux 3.3-rc1 (2012-01-19 15:04:48 -0800)
> >
> > are available in the git repository at:
> > git://git.open-mesh.org/linux-merge.git batman-adv-for-davem
>
> Somethings up:
>
> [davem@drr net-next]$ git pull git://git.open-mesh.org/linux-merge.git
> batman-adv-for-davem fatal: Couldn't find remote ref batman-adv-for-davem
>
> which is strange because I can see the tag there on git.open-mesh.org when
> I check it with my web browser.
Just tried it here (used linux-next for that) with git 1.7.9 and it worked
fine. Maybe you are using an older version of git? At least the error message
looks like it.
Have you tried:
git pull git://git.open-mesh.org/linux-merge.git tags/batman-adv-for-davem
But this will drop Mareks signature when done with an old git version (so no
merged tag is created).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-17 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 7:18 [B.A.T.M.A.N.] pull request: batman-adv 2012-02-17 Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 01/10] batman-adv: add tt_initialised flag to the orig_node struct Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 02/10] batman-adv: Explicitly mark the common header structure Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 03/10] batman-adv: simplify bat_ogm_receive API call Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 04/10] batman-adv: Rm empty line from is_my_mac() in main.c Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 05/10] batman-adv: Move is_out_of_time() to main.h for general use Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 06/10] batman-adv: warn if added interface is part of a bridge Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 07/10] batman-adv: add infrastructure to change routing algorithm at runtime Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 08/10] batman-adv: convert batman iv algorithm to use dynamic infrastructure Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 09/10] batman-adv: allowing changing the routing algorithm via module parameter Marek Lindner
2012-02-17 7:18 ` [B.A.T.M.A.N.] [PATCH 10/10] batman-adv: export used routing algorithm via sysfs Marek Lindner
2012-02-17 20:23 ` [B.A.T.M.A.N.] pull request: batman-adv 2012-02-17 David Miller
2012-02-17 20:44 ` Sven Eckelmann [this message]
2012-02-17 20:50 ` David Miller
2012-02-17 21:01 ` Mark Brown
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=1990573.JisbTKXt7B@sven-laptop.home.narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=lindner_marek@yahoo.de \
--cc=netdev@vger.kernel.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 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).