mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org, Uwe Kleine-Koenig <ukl@pengutronix.de>
Subject: Re: [PATCH] Add gpio command support to STM/i.MX arch
Date: Thu, 23 Dec 2010 12:58:40 +0100	[thread overview]
Message-ID: <4D133970.7090602@free-electrons.com> (raw)
In-Reply-To: <201012231250.08304.jbe@pengutronix.de>

On 12/23/2010 12:50 PM, Juergen Beisert wrote:
> Gregory CLEMENT wrote:
>> [...]
>>> are available in the git repository at:
>>>  http://git.pengutronix.de/git/jbe/for_barebox_next/ next_stm_gpio_v3
>>
>> I didn't manage to get your git tree:
>> $ git remote add -f jbe http://git.pengutronix.de/git/jbe/for_barebox_next
>> Updating jbe
>> fatal: http://git.pengutronix.de/git/jbe/for_barebox_next/info/refs
>> not found: did you run git update-server-info on the server?
>> error: Could not fetch jbe
>>
>> Indeed http://git.pengutronix.de/git/jbe/for_barebox_next/info/refs
>> does not exist.
>> Maybe I did something wrong or maybe be you have to run git
>> update-server-info on the server ;)
> 
> Sorry, I'm not a git expert. But this will show the content:
> 
> http://git.pengutronix.de/?p=jbe/for_barebox_next;a=summary
> 
> Don't know, what's wrong.
> 
> @Uwe: ?
> 

The problem was that I used http protocol instead of git protocol.
this command finally worked perfectly:
$git remote add -f jbe git://git.pengutronix.de/git/jbe/for_barebox_next

Thanks to Eric Bénard for his advice.


> jbe


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-12-23 11:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 11:25 Juergen Beisert
2010-12-21 11:25 ` [PATCH 1/9] Fix a typo in the GPIO doc Juergen Beisert
2010-12-21 11:25 ` [PATCH 2/9] ARM STM/i.MX: Fix register offset calculation for GPIO input pins Juergen Beisert
2010-12-21 11:25 ` [PATCH 3/9] ARM STM/i.MX: Remove variable size restrictions in iomux managing routines Juergen Beisert
2010-12-21 11:25 ` [PATCH 4/9] ARM STM/i.MX: Setting the iomux needs at least 32 bit Juergen Beisert
2010-12-21 11:25 ` [PATCH 5/9] ARM STM/i.MX: Just fix the docs Juergen Beisert
2010-12-21 11:25 ` [PATCH 6/9] ARM STM/i.MX: Add support for the gpio commands Juergen Beisert
2010-12-21 11:25 ` [PATCH 7/9] ARM STM/i.MX: Avoid very long lines Juergen Beisert
2010-12-21 11:25 ` [PATCH 8/9] ARM STM/i.MX: Replace cryptic numbers Juergen Beisert
2010-12-21 11:25 ` [PATCH 9/9] ARM Chumby: Add list of available GPIOs and their meaning Juergen Beisert
2010-12-23 11:30 ` [PATCH] Add gpio command support to STM/i.MX arch Gregory CLEMENT
2010-12-23 11:50   ` Juergen Beisert
2010-12-23 11:58     ` Gregory CLEMENT [this message]
2010-12-23 14:36     ` Uwe Kleine-König
2010-12-23 11:53   ` Eric Bénard

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=4D133970.7090602@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.de \
    --cc=ukl@pengutronix.de \
    /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