All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [GIT PULL] mpc83xx: reset status, 8360rev2.1 support, mpc8323erdb support, bugfixes
Date: Wed, 08 Aug 2007 11:57:47 -0400	[thread overview]
Message-ID: <46B9E7FB.9010807@gmail.com> (raw)
In-Reply-To: <20070808154940.91C7C352B18@atlas.denx.de>

Hi Wolfgang,

Wolfgang Denk wrote:
> In message <46B9DF69.3050507@gmail.com> you wrote:
>> Have you done Kim's pull request yet?  I don't see any evidence of it. 
> 
> No. I haven't. I haven't seen anything of it either.
> 
> When / where was it posted?

 From 2007-07-27:
<http://article.gmane.org/gmane.comp.boot-loaders.u-boot/30371>

>> WRT Kim's question on the -testing repo, what is the order or 
>> expectation for merges?  I've been expecting that the custodian repos 
>> will be pulled directly into the main repo and have been doing my 
>> pull/merges against that repo, not the testing repo.  If -testing is a 
>> stepping stone, I need to include that in my pull/merge to resolve any 
>> conflicts before they hit you.
> 
> Normally I pull the custodian repos into main, but ion the  last  few
> weeks  there  were  some  requests  that  required  code  that was in
> -testing only, so I pulled into -testin. But only on special request.
> Normal pull requests go always into mainline.

Good.  Thanks for the clarification.

> Best regards,
> 
> Wolfgang Denk

Best regards,
gvb

  reply	other threads:[~2007-08-08 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 23:23 [U-Boot-Users] [GIT PULL] mpc83xx: reset status, 8360rev2.1 support, mpc8323erdb support, bugfixes Kim Phillips
2007-08-08 15:21 ` Jerry Van Baren
2007-08-08 15:49   ` Wolfgang Denk
2007-08-08 15:57     ` Jerry Van Baren [this message]
2007-08-09 20:39 ` Wolfgang Denk
2007-08-10  2:33   ` Dave Liu
2007-08-10  8:30     ` Wolfgang Denk

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=46B9E7FB.9010807@gmail.com \
    --to=gvb.uboot@gmail.com \
    --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 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.