From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-sunxi.git/next
Date: Wed, 09 Jul 2014 07:58:52 +0100 [thread overview]
Message-ID: <1404889132.11981.2.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <53BC6301.9060907@myspectrum.nl>
On Tue, 2014-07-08 at 23:30 +0200, Jeroen Hofstee wrote:
> On 08-07-14 21:20, Ian Campbell wrote:
> > Hi Tom
> >
> > Sending to you for #next in Albert's absence.
> >
> > The following changes since commit 23f23f23d509e8e873797884456070c8a47d72b2:
> >
> > socfpga: Relocate arch common functions away from board (2014-07-05 10:14:46 +0200)
> >
> > are available in the git repository at:
> >
> > git://git.denx.de/u-boot-sunxi.git next
> >
> > for you to fetch changes up to 799aff38dfc1b2d860ec8430572f9402d3ce9881:
> >
> > sunxi: Avoid unused variable warning. (2014-07-08 07:45:06 +0100)
> >
>
> I am a bit lost here, why do want to send next branches for
> pull requests??
I discussed this with Albert on IRC and he said:
aaribaud: ijc: Re: next branches, you could push to next and
send a PR for my next indeed.
Ian.
next prev parent reply other threads:[~2014-07-09 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 19:20 [U-Boot] Please pull u-boot-sunxi.git/next Ian Campbell
2014-07-08 21:30 ` Jeroen Hofstee
2014-07-09 6:58 ` Ian Campbell [this message]
2014-07-16 19:31 ` Ian Campbell
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=1404889132.11981.2.camel@dagon.hellion.org.uk \
--to=ijc@hellion.org.uk \
--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