From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Microblaze] Pull Request: git://www.denx.de/git/u-boot-microblaze.git merge branch
Date: Sat, 13 Oct 2007 18:39:27 -0600 [thread overview]
Message-ID: <fa686aa40710131739u31ab087axe554ab04fbb6b2c5@mail.gmail.com> (raw)
In-Reply-To: <20071013205544.DCEA32408C@gemini.denx.de>
On 10/13/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <001101c7fe27$252a5760$0200a8c0@monstrone> you wrote:
> > Please pull from git://denx.de/git/u-boot-microblaze.git merge
>
> Please don't do that. Please put the stuff for me to merge in the
> master branch.
Really? It's perfectly reasonable for custodians to have multiple
branches and to request for you to pull from a specific one. This
becomes especially true with the adoption of the merge window process.
For instance, I have two branches on the 5xxx tree; one for bugfixes
to be merged immediately and another for stuff queued up for the next
window.
Besides, when someone uses git-request-pull (like Michal did) it's a
pretty trivial cut/paste to use git-pull to bring it into your branch.
It's not like it causes you extra work. :-)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-14 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 8:00 [U-Boot-Users] [PATCH] USB OHCI driver: Add NEC's PCI OHCI module ID David Saada
2007-09-16 14:02 ` Markus Klotzbücher
2007-09-16 15:23 ` Wolfgang Denk
2007-09-17 11:44 ` David Saada
2007-09-17 15:16 ` Markus Klotzbücher
2007-09-17 20:47 ` Wolfgang Denk
2007-09-19 8:55 ` [U-Boot-Users] [USB] Pull Request: git://www.denx.de/git/u-boot-usb.git Markus Klotzbücher
2007-09-22 22:51 ` Wolfgang Denk
2007-09-23 21:17 ` [U-Boot-Users] [Microblaze] Pull Request: git://www.denx.de/git/u-boot-microblaze.git merge branch Michal Simek
2007-10-13 20:55 ` Wolfgang Denk
2007-10-14 0:39 ` Grant Likely [this message]
2007-10-14 9:16 ` Wolfgang Denk
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=fa686aa40710131739u31ab087axe554ab04fbb6b2c5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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