U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Conflict resolution for u-boot-arm/master and u-boot/master merge
Date: Thu, 30 May 2013 19:37:48 +0200	[thread overview]
Message-ID: <20130530193748.37046c97@lilith> (raw)
In-Reply-To: <CAPnjgZ0OoSHYuLBCB7L8gAJr0RMQETd-tC-MA7BmFy=boDS4qQ@mail.gmail.com>

Hi Simon,

On Thu, 30 May 2013 09:38:56 -0700, Simon Glass <sjg@chromium.org>
wrote:

> Hi Albert,
> 
> On Thu, May 30, 2013 at 9:21 AM, Albert ARIBAUD
> <albert.u.boot@aribaud.net>wrote:
> 
> > On Thu, 30 May 2013 14:55:41 +0200, Albert ARIBAUD
> > <albert.u.boot@aribaud.net> wrote:
> >
> > > Hello Tom and Bo,
> > >
> > > While preparing for my ARM PR, I have encountered two merge conflicts.
> > > Their resolution can be found in branch 'merge_from_mainline' of ARM
> > > repo git://git.denx.de/u-boot-arm.
> > >
> > > For common/cmd_fpga.c, the merge conflict was trivial -- Simon's
> > > renaming fit somehow caused a need for manual resolution just to
> > > select the version with the right name. Simon, can you confirm that my
> > > resolution is correct?
> >
> > ... actually adding Simon as To:...
> >
> 
> Yes this looks right thanks.

Thanks for your confirmation.

> Although I do wonder if you mean that I renamed 'fit', or I had a renaming
> fit.

Phew! I was wondering if that one had gone below everyone's radars. :)

> Regards,
> Simon

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-05-30 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 12:55 [U-Boot] Conflict resolution for u-boot-arm/master and u-boot/master merge Albert ARIBAUD
2013-05-30 13:03 ` Tom Rini
2013-05-30 13:33 ` Bo Shen
2013-05-30 16:21 ` Albert ARIBAUD
2013-05-30 16:38   ` Simon Glass
2013-05-30 17:37     ` Albert ARIBAUD [this message]
2013-05-31  1:08       ` Simon Glass

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=20130530193748.37046c97@lilith \
    --to=albert.u.boot@aribaud.net \
    --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