All these git related puns are killing me :-)
On Fri, Apr 8, 2011 at 8:46 AM, Will Deacon <will.deacon(a)arm.com> wrote:
> > On Fri, Apr 8, 2011 at 3:45 PM, Tixy <tixy(a)yxit.co.uk> wrote:
> > > On Fri, 2011-04-08 at 10:16 +0100, Dave Martin wrote:
> > >> one reason why my understanding of the actual problem here was a bit
> > >> patchy.
> > >
> > > <groan> :-)
> >
> > _not_ intentional! (if you believe me)
>
> I don't believe you; I think you should consider branching out
> into comedy...
>
> Will
>
>
>
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev(a)lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev
>
Enclosed you'll find a link to the agenda, minutes and actions from the
Linaro Toolchain working group weekly meetings of April 04 & 07, 2011.
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-04https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-07
== Summary ==
* More vectoriser patches including if-conversion, different vector sizes,
and vzip/vunzip are going upstream
* Chung-Lin continues to knock off a good set of bugs
* QEMU consolidation continues
* A fair set of patches were accepted upstream recently
* The OMAP3 patch set has been split further up.
* A separate set of discussions on Thumb-2 performance improvements will
start soon
* Andrew is running a Linaro Android baseline build to prepare for the
Android GCC patches later
* Linaro GCC 4.6 is being updated to the new FSF 4.6 release branch
* Cleaning up the libunwind testsuite for use exercising the ARM port
Regards,
Mounir
Hi all,
I've encountered a problem trying to unpick the history of the linaro
git trees, but I don't think it's specific to us:
The problem seems to be that when a merge is committed, git references
the merged commits in their original context: no information is
recorded about how the merge was resolved. The result just appears by
magic as the new tree recorded for the merge commit.
This seems to mean that git format-patch x..y (where x is an ancestor
of y) does _not_ necessarily give you a patch series which actually
applies on x (indeed, the generated patch series may not be appliable
on any commit, in any order). This is certainly my experience.
As a result, it seems very difficult to pick apart the history of a
branch beyond the last merge commit, because the git repo only records
the logical ancestry (i.e., which upstream patches got merged) rather
than any "physical" history (i.e., what sequence of actual changes
would be needed to reconstruct the branch). In fact, it seems to be
nonsense to think in terms of a sequence of patches beyond a merge
commit.
What I'm actually trying to do is cherry-pick a few omap- and Thumb-
specific commits out of the linaro tree to apply on v2.6.39-rc2 --
just the minimum subset so that I can develop Thumb stuff on a tree
which is as clean and close to upstream as possible. But I repeatedly
run into problems where patch p from branch b depends on
cherry-picking some other patch q merged branch b, but the cherry pick
fails since the actual delta recorded for q is in the context of
someone else's branch (the branch that was merged from).
If anyone knows a straightforward way to achieve this, I'd be interested ...
Of course, I may be trying to do entirely the wrong thing.
Cheers
---Dave
FYI:
----- Forwarded message from Gunnar Wolf <gwolf(a)debian.org> -----
Date: Thu, 7 Apr 2011 14:16:33 -0500
From: Gunnar Wolf <gwolf(a)debian.org>
To: debian-devel-announce(a)lists.debian.org
Subject: Registration now open for DebConf11
User-Agent: Mutt/1.5.20 (2009-06-14)
Registration is now open for DebConf11. For registration instructions,
please see:
http://debconf11.debconf.org/register.xhtml
DebConf11 will take place in Banja Luka, in Republika Srpska, Bosnia
and Herzegovina from Sunday 24th to Saturday 30th July, 2011. DebConf
will be preceded by DebCamp, from Sunday 17th to Saturday 23rd July,
2011. DebCamp is a smaller, less formal event intended for group work
on Debian projects.
The sponsored registration deadline is 8 May.
Again, this year, we will have basic, sponsored, professional (€450),
and corporate (€1000) registration categories. Travel sponsorship is
again available.
----- End forwarded message -----
Cheers,
--
Steve McIntyre
steve.mcintyre(a)linaro.org
Hi David & all:
A recent blog post by Andy Rubin may help alleviating some concern on Google’s position on Android:
http://android-developers.blogspot.com/2011/04/i-think-im-having-gene-amdah…
Regarding ChromeOS, I haven’t looked at it myself at all. But as far as I know, the ChromeOS image will be digitally signed by Google; so it’s unlikely for any 3rd party to release a creditable ChromeOS build without Google authorization. The Chromium OS project is the open source version of it (http://www.chromium.org/chromium-os/developer-guide). Disregard my comment, if ChromimuOS is already what you guys are working on.
Best regards,
Alan Chuang
-----Original Message-----
From: linaro-dev-bounces(a)lists.linaro.org [mailto:linaro-dev-bounces@lists.linaro.org] On Behalf Of David Rusling
Sent: 2011年4月7日GMT+08:00下午10時14分12秒
To: "linaro-dev(a)lists.linaro.org<mailto:linaro-dev@lists.linaro.org>" <linaro-dev(a)lists.linaro.org<mailto:linaro-dev@lists.linaro.org>>
Subject: Office of CTO meeting notes
All,
the minutes of the last meeting can be found here -
https://wiki.linaro.org/OfficeofCTO/2011-04-05
Dave
--
David Rusling, CTO
http://www.linaro.org
Linaro
Lockton House
Clarendon Rd
Cambridge
CB2 8FH
_______________________________________________
linaro-dev mailing list
linaro-dev(a)lists.linaro.org<mailto:linaro-dev@lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-dev
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Gang,
Exciting news... we have a test instance of our wiki with upgraded
software just waiting for you to test out and find bugs!
https://wiki-test.linaro.org/
If testing goes well we'll upgrade the wiki NEXT WEEK. All changes to
the test wiki will be thrown away so feel free to be destructive.
Also, if you've been complaining about the wiki being broken, now's
your chance to see if there are still problems with this newer
version.
Known Issues:
1) The calendars will need a tweak. Right now you'll get an error like this:
<<MonthCalendar: execution failed [Argument "anniversary" must be a
boolean value, not "projectmanagement/meetings/meetingtemplate"] (see
also the log)>>
2) The column macro (like the one we use on the front page) needs some
tweaking after the upgrade. The front page has been tweaked on the
test wiki.
Thanks!
Joey
Hi Everybody,
There will be a Introduction to Linaro@UDS presentation next week.
This presentation is mainly directed at employees who have not
attended a summit in the past, but all are welcome to attend.
There will be a presentation of the slides linked below followed
by a question/answer session. The meeting times are:
Wednesday: 13 April 2011 4:00 UTC
Thursday: 14 April 2011 15:00 UTC
https://docs.google.com/present/view?id=dfg534bg_21f49t9krd
Cheers,
Matt
The variable TARGET_ARCH_VERSION variable has been renamed to
TARGET_ARCH_VARIANT, and armv7-a-neon is the exact target enables
ARM NEON instructions.
Also, do include header <machine/cpu-features.h> to get ARM optimized
routines compiled.
Code Review:
https://review.source.android.com/#change,22208