Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ARC: bump tools to 2014.08 release
Date: Tue, 26 Aug 2014 21:53:20 +0000	[thread overview]
Message-ID: <1409090000.3760.1.camel@abrodkin-8560l> (raw)
In-Reply-To: <87d2bmvs2f.fsf@dell.be.48ers.dk>

Hi Peter,

On Tue, 2014-08-26 at 23:50 +0200, Peter Korsgaard wrote:
> >>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> 
> Hi,
> 
>  >> > I'm wondering if there's still a chance to get this patch applied before
>  >> > 2014.08 release?
>  >> 
>  >> My feeling is that it was submitted too late to get applied to 2014.08.
>  >> Generally speaking, we don't merge any version bump after -rc1 has been
>  >> tagged, unless those bumps are known to fix important issues.
>  >> 
>  >> Therefore, I believe this change qualifies for the next branch, and
>  >> will therefore be part of the 2014.11 Buildroot release.
> 
>  > Sure, makes perfect sense!
> 
>  > Unfortunately we were a bit late with our release so yes let's apply it
>  > to the next.
> 
> I agree. The current patch doesn't apply to next. Care to rebase and
> resend?

Do I have any options? :)

I mean anyway after you guys cut final 2014.08 release "next" branch
will be merged with current master, right?

If so I have no other choice other than rebase and resend.
Correct me if I'm wrong.

-Alexey

  reply	other threads:[~2014-08-26 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 17:33 [Buildroot] [PATCH v2] ARC: bump tools to 2014.08 release Alexey Brodkin
2014-08-26 14:49 ` Alexey Brodkin
2014-08-26 14:58   ` Thomas Petazzoni
2014-08-26 15:01     ` Alexey Brodkin
2014-08-26 21:50       ` Peter Korsgaard
2014-08-26 21:53         ` Alexey Brodkin [this message]
2014-08-26 22:02           ` Peter Korsgaard
2014-08-26 22:04             ` Alexey Brodkin
2014-09-01  7:00             ` Alexey Brodkin
2014-09-01 14:52               ` Peter Korsgaard
2014-09-01 14:53 ` Peter Korsgaard

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=1409090000.3760.1.camel@abrodkin-8560l \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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