From: Gernot Hillier <gernot.hillier@siemens.com>
To: xenomai@xenomai.org
Subject: [Xenomai] missing branches in ipipe.git when fetching via http from xenomai.org
Date: Mon, 23 Sep 2013 16:03:50 +0200 [thread overview]
Message-ID: <52404A46.3050801@siemens.com> (raw)
Hi there!
Sorry if this is the wrong place to report server problems. Please let
me know whom to contact if this is the case...
When fetching ipipe via http://, I miss the ipipe-3.8 branch:
> git remote add ipipe http://git.xenomai.org/ipipe.git
> git remote update ipipe
[...]
> git branch -a | grep 3.8
remotes/ipipe/ipipe-3.8.0
> git remote rm ipipe
When using git://, everything works as expected:
> git remote add ipipe git://git.xenomai.org/ipipe.git
> git remote update ipipe
[...]
> git branch -a | grep 3.8
remotes/ipipe/ipipe-3.8
remotes/ipipe/ipipe-3.8.0
Unfortunately, our Siemens firewall forces us to http in most cases - so
it would be great if you could fix it... TIA!
--
With kind regards,
Gernot Hillier
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2013-09-23 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 14:03 Gernot Hillier [this message]
2013-09-23 22:55 ` [Xenomai] missing branches in ipipe.git when fetching via http from xenomai.org Gilles Chanteperdrix
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=52404A46.3050801@siemens.com \
--to=gernot.hillier@siemens.com \
--cc=xenomai@xenomai.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.