From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull 85xx
Date: Wed, 02 Jan 2008 19:04:15 +0100 [thread overview]
Message-ID: <477BD21F.7040205@semihalf.com> (raw)
In-Reply-To: <20080102151213.7F68524755@gemini.denx.de>
Dear Wolfgang,
you wrote:
*snip*
>> Anyway, I'm fine with whatever policy we want to follow. But if this
>> happens again, I'd like to know what to do. :) I can always just create a
>> side tree which has the latest state of development, while I wait for any
>> dependent changes to propagate into the mainline.
>
> Well, let's try this:
>
> If your work depends on patches from another repo, please ask the
> custodian of this other repo to send a pull request, and ask him to
> mention in his pull request that this is urgent becasue ... depends
> on it.
>
I guess I'm still a bit confused about the process. So in case of inter-repo
dependencies, would you like something like the following?
1. ask the involved custodian(s) to merge my pieces that I depend on, but that
belong to different FA, and have them send pull requests to you
2. you merge those onto the testing branch
Should I then rebase against the testing repo, or wait until it makes to the
main line and only then come up with my pull request? (as there's a general
rule for pull requests to be based on the main line..). Please clarfiy.
kind regards,
Rafal
next prev parent reply other threads:[~2008-01-02 18:04 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
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 [this message]
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=477BD21F.7040205@semihalf.com \
--to=raj@semihalf.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.