From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Brodkin Date: Tue, 26 Aug 2014 21:53:20 +0000 Subject: [Buildroot] [PATCH v2] ARC: bump tools to 2014.08 release In-Reply-To: <87d2bmvs2f.fsf@dell.be.48ers.dk> References: <1408642436-2489-1-git-send-email-abrodkin@synopsys.com> <1409064582.6466.21.camel@abrodkin-8560l.internal.synopsys.com> <20140826165826.398f7a63@free-electrons.com> <1409065267.6466.23.camel@abrodkin-8560l.internal.synopsys.com> <87d2bmvs2f.fsf@dell.be.48ers.dk> Message-ID: <1409090000.3760.1.camel@abrodkin-8560l> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi Peter, On Tue, 2014-08-26 at 23:50 +0200, Peter Korsgaard wrote: > >>>>> "Alexey" == Alexey Brodkin 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