public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull 85xx
Date: Thu, 27 Dec 2007 19:22:50 +0100	[thread overview]
Message-ID: <200712271922.50572.sr@denx.de> (raw)
In-Reply-To: <20071227170446.0C94A24889@gemini.denx.de>

On Thursday 27 December 2007, Wolfgang Denk wrote:
> > That can be very hard sometimes. Please note that I had the same problem
> > and also included the libfdt changes from Kumar into the 4xx for-1.3.2
> > branch, since this brings all this fdt work to a very nice status.
> > Without it, it is nearly impossible to do any decent fdt stuff anymore.
> > And since you didn't pull the changes from Jerry into the master or
> > testing repository at that time, we *had* to do something to have a
> > chance to get the stuff ready for merging within the merge window.
>
> But when you pull any other repository into your tree, you leave me no
> option wether I want to accept this repo as iis or request changes or
> if I want to omit parts of it for one reason or another.
>
> When I'm pulling the libfdt repo, I will check what's in there, but
> when I pull the 4xx repo, I do NOT want to have to check any other
> repo in parallel, too.

If I understand this correctly, then recent git versions are capable of 
handling such cases without problems. Meaning pulling patches from another 
repo, that are allready present should cause no problems.

> Sorry, if there are such dependencies, then please drop me a note and
> we will find a way to dort it out. YOu know that I will try  to  help
> if somebody has a reasonable request.

I did ask you once or twice about this fdt repo, but I should have have been 
more insistant.

> The current situation is not acceptable to me. The custodian  reposi-
> tories  are supposed to be strictly orthogonal to each other. If they
> are not, I will refuse to pull.

Right. Generally I share this opinion. All this is probably something we have 
to "learn" in the next few merge windows.

I'll try to remove the already commited fdt patches from my repo and merge 
with mainline before asking you to pull from the 4xx repo. OK?

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-12-27 18:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12  5:41 [U-Boot-Users] Please pull 85xx Andy Fleming
2007-12-12 13:37 ` Jerry Van Baren
2007-12-26 23:38 ` Wolfgang Denk
2007-12-27 16:01   ` Stefan Roese
2007-12-27 17:04     ` Wolfgang Denk
2007-12-27 18:22       ` Stefan Roese [this message]
2007-12-27 20:12         ` Wolfgang Denk
2007-12-29 21:49   ` Andy Fleming
2008-01-02 15:12     ` Wolfgang Denk
2008-01-02 18:04       ` Rafal Jaworowski
2008-01-02 20:09         ` Wolfgang Denk
2008-01-02 20:52           ` Jerry Van Baren
2008-01-03 15:15             ` Haavard Skinnemoen

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=200712271922.50572.sr@denx.de \
    --to=sr@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