public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Getting ready for -rc1
Date: Tue, 06 Dec 2011 23:56:46 +0200	[thread overview]
Message-ID: <4EDE8F9E.6070009@mleia.com> (raw)
In-Reply-To: <4EDE8D2A.6000105@aribaud.net>

Hi Albert,

thank you for response.

On 06.12.2011 23:46, Albert ARIBAUD wrote:
> Le 06/12/2011 16:17, Wolfgang Denk a ?crit :
>> Dear Vladimir,
>>
>> In message<4EDE21C1.6010809@mleia.com>
>> (sfid-20111206_140838_823869_D329B307) you wrote:
>>>
>>>> You should not ask me, but the responsible custodian.
>>>
>>> please excuse me, but sometimes I have to ask you, often you're the last
>>> resort in getting feedback relatively to my crap.
>>
>> Don't take my words literally, please ;-)
>>
>> But for ARM boards I really tend to just wait for a pull request from
>> Albert.
>
> (is my old free.fr email address still lingering somewhere?)
>
> Vladimir,
>
> If I am not mistaken, these are not bug fixes, and were submitted after
> the merge window was closed. Unless Wolfgang agrees that I let them in
> now, they should wait until next merge window.

Surely I don't insist in inclusion of the SoC support into this release, 
but I have a hope to get it in the next, and the next merge window start 
is expected to be on the next week or so, if I'm not mistaken.

I rebased the changes a couple of times upon u-boot-arm/next, I thought 
that this branch is dedicated for the next merge window changes, but my 
change still haven't been pushed into it, that's why I feel worried 
about them and their inclusion during the next merge window.

I just would be glad to get awared eventually that from your ARM 
custodian perspective the proposed change is ok for U-boot.

-- 
With best wishes,
Vladimir

  parent reply	other threads:[~2011-12-06 21:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 11:12 [U-Boot] [STATUS] Getting ready for -rc1 Wolfgang Denk
2011-12-06 11:44 ` Graeme Russ
2011-12-06 21:24   ` Graeme Russ
2011-12-06 21:28   ` Albert ARIBAUD
2011-12-06 21:33     ` Graeme Russ
2011-12-06 21:52       ` Albert ARIBAUD
2011-12-06 12:28 ` Igor Grinberg
2011-12-06 13:22 ` Vladimir Zapolskiy
2011-12-06 13:35   ` Wolfgang Denk
2011-12-06 14:08     ` Vladimir Zapolskiy
2011-12-06 15:17       ` Wolfgang Denk
2011-12-06 21:46         ` Albert ARIBAUD
2011-12-06 21:50           ` Wolfgang Denk
2011-12-06 21:56           ` Vladimir Zapolskiy [this message]
2011-12-06 22:15             ` Albert ARIBAUD
2011-12-06 22:18               ` Vladimir Zapolskiy
2011-12-06 16:44 ` Jason Hobbs
2011-12-07  1:13 ` Simon Glass
2011-12-07  3:12 ` Macpaul Lin
2011-12-07 10:05 ` Andreas Bießmann
2011-12-07 10:25   ` Wolfgang Denk
     [not found] ` <4EDF3855.5010202@corscience.de>
2011-12-07 10:25   ` Wolfgang Denk
2011-12-07 10:51     ` Andreas Bießmann
2011-12-07 12:11       ` Wolfgang Denk
2011-12-07 12:14         ` Andreas Bießmann
2011-12-07 12:35           ` Wolfgang Denk
2011-12-07 13:20       ` Sven Schnelle
2011-12-07 13:41         ` Andreas Bießmann
  -- strict thread matches above, loose matches on Subject: below --
2011-05-16 20:24 Wolfgang Denk
2011-05-17 17:04 ` Andreas Pretzsch
2011-05-17 21:33   ` Jerry Van Baren

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=4EDE8F9E.6070009@mleia.com \
    --to=vz@mleia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox