All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-sunxi.git/master
Date: Thu, 31 Jul 2014 10:09:25 +0200	[thread overview]
Message-ID: <53D9F9B5.5040500@redhat.com> (raw)
In-Reply-To: <1406793249.28644.57.camel@dagon.hellion.org.uk>

Hi,

On 07/31/2014 09:54 AM, Ian Campbell wrote:
> On Thu, 2014-07-31 at 13:30 +0900, Masahiro Yamada wrote:
>> Hi Tom, Albert, Hans,
>>
>>
>> I am afraid we are going to be in trouble
>> with this pre-Kconfig based PR
>> because it includes various new boards.
> 
> Yeah, I was wondering how this would work!
> 
>> (We can fix the merge conflict,
>> but it is not trivial.)
>>
>>
>> How this is going to work?
>>
>> Perhaps should we discard unmerged PRs and
>> get all the subsystem repos
>> synchronized with u-boot/master ?
>>
>>
>> Or shall we break these boards once
>> and fix them in a follow-up patch ?
> 
> Can you point us to the conversion script please?
> 
> (I say "us/we" here but I'm actually about to get on a plain and be AFK
> for several days, so I guess I mean "Hans" ;-))
> 
> With that script we could rebase onto the current branch base running
> the script at every step (including a new artificial step right before
> the top of the branch to pickup all the other boards) and commit --amend
> any new defconfigs which are produced.
> 
> Then rebase the result of that onto the current master, ignoring
> conflicts in boards.cfg (i.e. just deleting it each time).
> 
> The result should be a rebased tree where all the changes to boards.cfg
> are instead replicated in the appropriate defconfig.
> 
> Does that sound workable?

That sounds workable to me. I can try to get that done this weekend,
and then send a new PR rebased on current master.

Regards,

Hans

  reply	other threads:[~2014-07-31  8:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  8:37 [U-Boot] Please pull u-boot-sunxi.git/master Hans de Goede
2014-07-31  4:30 ` Masahiro Yamada
2014-07-31  7:54   ` Ian Campbell
2014-07-31  8:09     ` Hans de Goede [this message]
2014-07-31  8:23     ` Masahiro Yamada
2014-07-31 14:25       ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2014-09-05 13:23 Ian Campbell
2014-09-09  7:58 ` Albert ARIBAUD
2014-09-09  8:27   ` Ian Campbell
2014-08-28 21:17 Hans de Goede
2014-08-12  8:36 Hans de Goede
2014-08-29 17:48 ` Tom Rini
2014-07-31 14:30 Hans de Goede
2014-08-01  1:54 ` Masahiro Yamada
2014-08-09 13:41   ` Albert ARIBAUD
2014-08-09 16:42 ` Albert ARIBAUD
2014-07-18 19:14 Ian Campbell
2014-07-18 19:45 ` Siarhei Siamashka
2014-07-18 20:05   ` Ian Campbell
2014-07-28  8:53 ` Albert ARIBAUD

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=53D9F9B5.5040500@redhat.com \
    --to=hdegoede@redhat.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.