public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Custodians - please lend a hand
Date: Thu, 17 Nov 2011 19:19:31 +0100	[thread overview]
Message-ID: <m24ny2pq6k.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4EC4102D.2020903@denx.de> (Stefano Babic's message of "Wed, 16 Nov 2011 20:34:05 +0100")

Hi Stefano,

> On 11/16/2011 07:51 PM, Wolfgang Denk wrote:
>
> Wolfgang,
>
>>>
>>> Please let's try if this works.  If you have any suggestions how to
>>> help better, please don't hesitate to tell us.
>
> I have tried with a couple of patches (network related), and then I 
> wanted to test if push works. As u-boot-staging should be open for all 
> custodians, I was expecting I should use the same mechanism, and then I 
> tried with:
>
>
> git push ssh://gu-imx at git.denx.de/u-boot-staging sbabic at denx.de
>
> ...but the new branch sbabic at denx.de is now part of u-boot-imx, not 
> u-boot-staging ! Where is the mistake ?

Indeed - this is because of the setup of the custodian trees.  The git
action is directly coupled to the user account so the account gu-imx
will _only_ be able to work inside that tree.  Effectively, the
directory part of the URL is discarded...

The correct usage is of course as Wolfgang points out through the
gu-staging user.

Best wishes
  Detlev

-- 
Due to the change in scope, STUN has also been renamed from "Simple Traversal
of UDP through NAT" to  "Session  Traversal Utilities for NAT".   The acronym
remains STUN, which is all anyone ever remembers anyway.    -- rfc5389
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  parent reply	other threads:[~2011-11-17 18:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  6:21 [U-Boot] Application of patch submitted during the previous Merge Window Graeme Russ
2011-09-23  7:25 ` Wolfgang Denk
2011-09-23  9:21   ` Graeme Russ
2011-09-23 10:04     ` Stefano Babic
2011-09-23 10:17       ` Graeme Russ
2011-09-23 10:23       ` Wolfgang Denk
2011-09-25 10:24         ` stefano babic
2011-09-23 10:18     ` Wolfgang Denk
2011-09-23 10:46       ` Graeme Russ
2011-09-25 19:55         ` Wolfgang Denk
2011-09-25 20:32           ` Graeme Russ
2011-09-30 22:40           ` Mike Frysinger
2011-11-15 15:01         ` [U-Boot] [STATUS] Help needed - urgently Wolfgang Denk
2011-11-16 18:51           ` [U-Boot] [STATUS] Custodians - please lend a hand Wolfgang Denk
2011-11-16 19:34             ` Stefano Babic
2011-11-16 19:48               ` Wolfgang Denk
2011-11-17 18:19               ` Detlev Zundel [this message]
2011-11-17 20:16                 ` Andy Fleming
2011-11-17 20:58                   ` Wolfgang Denk
2011-11-16 20:38           ` [U-Boot] [STATUS] Help needed - urgently Kumar Gala
2011-11-16 21:35             ` Wolfgang Denk
2011-11-17 12:40               ` Stefano Babic
2011-11-17 13:41                 ` Kumar Gala
2011-11-17 13:43               ` Kumar Gala
2011-11-17 14:10                 ` Wolfgang Denk
2011-11-17 14:54                   ` Kumar Gala

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=m24ny2pq6k.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=u-boot@lists.denx.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