From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Add gpio command support to STM/i.MX arch
Date: Thu, 23 Dec 2010 15:36:08 +0100 [thread overview]
Message-ID: <20101223143608.GV14221@pengutronix.de> (raw)
In-Reply-To: <201012231250.08304.jbe@pengutronix.de>
On Thu, Dec 23, 2010 at 12:50:07PM +0100, 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?
^^^^^^^^^^^^^^^^^^^^^^
you only need to believe this :-)
> > 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: ?
You need to do
cd /path/to/your/for_barebox_next-repo
git update-server-info
(to fix this for now and )
mv hooks/post-update.sample hooks/post-update
(to assert it stays fixed when you push the next time.)
But in general git:// is preferable because it only transfers the needed
objects (in contrast to the complete history when the repository is
perfectly packed even you only miss a single object).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-12-23 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 11:25 [PATCH] Add gpio command support to STM/i.MX arch 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
2010-12-23 14:36 ` Uwe Kleine-König [this message]
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=20101223143608.GV14221@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jbe@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 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.