similar to: [LLVMdev] [3.2 Release] T-11 days and counting

Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] [3.2 Release] T-11 days and counting"

2019 Aug 13
2
DANGER WILL ROBINSON, DANGER
On 09/08/19 18:24, Matthew Wilcox wrote: > On Fri, Aug 09, 2019 at 07:00:26PM +0300, Adalbert Laz?r wrote: >> +++ b/include/linux/page-flags.h >> @@ -417,8 +417,10 @@ PAGEFLAG(Idle, idle, PF_ANY) >> */ >> #define PAGE_MAPPING_ANON 0x1 >> #define PAGE_MAPPING_MOVABLE 0x2 >> +#define PAGE_MAPPING_REMOTE 0x4 > Uh. How do you know page->mapping would
2019 Aug 13
2
DANGER WILL ROBINSON, DANGER
On 09/08/19 18:24, Matthew Wilcox wrote: > On Fri, Aug 09, 2019 at 07:00:26PM +0300, Adalbert Laz?r wrote: >> +++ b/include/linux/page-flags.h >> @@ -417,8 +417,10 @@ PAGEFLAG(Idle, idle, PF_ANY) >> */ >> #define PAGE_MAPPING_ANON 0x1 >> #define PAGE_MAPPING_MOVABLE 0x2 >> +#define PAGE_MAPPING_REMOTE 0x4 > Uh. How do you know page->mapping would
2013 Jan 13
3
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
Pawel, We all understand that you're pretty new to release process, etc., but I think you should understand the implications of your actions. You just created a lot of harm for really huge pile of users - the ones who downloads the tarball via some automated build system and rely on the known good checksum. This includes, but not limited to to the users of FreeBSD, Gentoo, etc. Even worse,
2013 Jan 13
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
Anton, > Pawel, > > We all understand that you're pretty new to release process, etc., but > I think you should understand the implications of your actions. > > You just created a lot of harm for really huge pile of users - the > ones who downloads the tarball via some automated build system and > rely on the known good checksum. This includes, but not limited to to
2012 Nov 17
0
[LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
On Nov 16, 2012, at 3:52 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > >>> This approach is fine for casual reader but >>> does not work for scripting or any automated >>> way of dealing with the build. >> Will you please clarify how the automation / scripting helps with the >> patch approval process? > > > Generally release patch
2013 Jan 11
2
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On Fri, Jan 11, 2013 at 3:47 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > On 1/11/2013 2:40 PM, Brooks Davis wrote: > > On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote: > >> > >> On 11.01.2013, at 21:31, Justin Holewinski > >> <justin.holewinski at gmail.com> wrote: > >> > >>> On Fri, Jan 11, 2013 at 3:26
2012 Dec 04
0
[LLVMdev] [cfe-dev] !!! 3.2 Release - Release Notes, Documentation, External Projects and the RC3
Alright, can you please pull in r169280? On Tue, Dec 4, 2012 at 12:56 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > On 12/4/2012 10:14 AM, Justin Holewinski wrote: > > What is the procedure for updating the release notes? I've been > committing > > changes to the trunk version, should I be editing them elsewhere? Or > will > > the trunk version be
2005 Jun 10
1
Re: Voicemail and MS Exchange Synchronizatio n
> -----Original Message----- > From: Iassen Hristov [mailto:ih.ng@databrokers.net] Dumb, hacky idea...but just so crazy it might work: Have Asterisk include a read receipt request when sending the voice mail message. Write a script, triggered from a sendmail alias or .forward file, that will parse the incoming receipts and handle the message deletion. Bonus points: When someone listens
2019 Aug 13
0
DANGER WILL ROBINSON, DANGER
On Tue, Aug 13, 2019 at 11:29:07AM +0200, Paolo Bonzini wrote: > On 09/08/19 18:24, Matthew Wilcox wrote: > > On Fri, Aug 09, 2019 at 07:00:26PM +0300, Adalbert Laz?r wrote: > >> +++ b/include/linux/page-flags.h > >> @@ -417,8 +417,10 @@ PAGEFLAG(Idle, idle, PF_ANY) > >> */ > >> #define PAGE_MAPPING_ANON 0x1 > >> #define
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 1/11/2013 2:51 PM, Justin Holewinski wrote: > On Fri, Jan 11, 2013 at 3:47 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > >> On 1/11/2013 2:40 PM, Brooks Davis wrote: >>> On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote: >>>> >>>> On 11.01.2013, at 21:31, Justin Holewinski >>>> <justin.holewinski at
2012 Nov 18
0
[LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
On Sat, Nov 17, 2012 at 7:40 PM, Pawel Wodnicki <pawel at 32bitmicro.com>wrote: > On 11/17/2012 6:35 PM, Chris Lattner wrote: > > > > On Nov 17, 2012, at 9:57 AM, Nadav Rotem <nrotem at apple.com> wrote: > > > >> I think that the code owner process is becoming complicated and I am > not sure if it serves Chris's original intent. I don't think
2009 Feb 09
2
Counting session days
hi, I have some session data in a dataframe, where each session is recorded with a start and a stop date. Like this: session_start session_stop =================== 2009-01-03 2009-01-04 2009-01-01 2009-01-05 2009-01-02 2009-01-09 A session is at least one day long. Now I want a dataframe with 'active sessions' per date. Like this: date active_sessions ============= 2009-01-01 1
2012 Dec 04
2
[LLVMdev] [cfe-dev] !!! 3.2 Release - Release Notes, Documentation, External Projects and the RC3
On 12/4/2012 10:14 AM, Justin Holewinski wrote: > What is the procedure for updating the release notes? I've been committing > changes to the trunk version, should I be editing them elsewhere? Or will > the trunk version be merged in? The exact procedure is not spelled out but I think the easiest would be to merge relevant "ReleaseNotes.html" changes from the trunk,
2012 Nov 18
2
[LLVMdev] [cfe-dev] !!! 3.2 Release branch patching and the Code Owners
On 11/17/2012 6:35 PM, Chris Lattner wrote: > > On Nov 17, 2012, at 9:57 AM, Nadav Rotem <nrotem at apple.com> wrote: > >> I think that the code owner process is becoming complicated and I am not sure if it serves Chris's original intent. I don't think that we need to change every file nor do we need an automatic tool to find the owner. I think that a simple text
2012 Nov 30
1
[LLVMdev] !!! 3.2 Release RC2 deadline November 29th
Akira, > Pawel, > > Is it still not too late to merge these patches? > > r168471 > r168460 > r168458 > r168456 > r168455 > r168453 > r168450 > r168448 > > These patches fix a bug in mips backend's GOT implementation and add > support for big-GOT relocations. That's quite a list of patches! To get them into the 3.2 release you would first
2012 Nov 15
0
[LLVMdev] missing polly 3.2 branch?
On Nov 13, 2012, at 11:16 AM, Pawel Wodnicki <pawel at 32bitmicro.com> wrote: > Bill, > >> Hi Pawel, >> >> Could you branch polly as well for the 3.2 release? We will need to contact the 'polly' guys to figure out how best to add it to the release (testing, etc.). > > Sure. > > But I do not know much about polly so 'polly' guys please
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 1/11/2013 3:59 PM, Brooks Davis wrote: > On Fri, Jan 11, 2013 at 02:47:01PM -0600, Pawel Wodnicki wrote: >> On 1/11/2013 2:40 PM, Brooks Davis wrote: >>> On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer >>> wrote: >>>> >>>> On 11.01.2013, at 21:31, Justin Holewinski >>>> <justin.holewinski at gmail.com> wrote:
2013 Jan 13
2
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
Pawel, First, all your help with the 3.2 release is greatly appreciated. I do not think anyone is saying otherwise. I apologize for the lack of documentation regarding this issue. I do ask that you consult with previous release manager (myself or Bill) to determine what the best course of action is. There is a lot of room to improve our release process, but its a collaborative effort. You are
2012 Nov 30
0
[LLVMdev] !!! 3.2 Release RC2 deadline November 29th
Pawel, Is it still not too late to merge these patches? r168471 r168460 r168458 r168456 r168455 r168453 r168450 r168448 These patches fix a bug in mips backend's GOT implementation and add support for big-GOT relocations. Thank you. On Tue, Nov 27, 2012 at 7:35 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > Hello, > > Just a quick reminder that the November 29th
2012 Nov 13
2
[LLVMdev] missing polly 3.2 branch?
Bill, > Hi Pawel, > > Could you branch polly as well for the 3.2 release? We will need to contact the 'polly' guys to figure out how best to add it to the release (testing, etc.). Sure. But I do not know much about polly so 'polly' guys please fill me on the details. For the 3.2 release I will need: - to know how to build it seems to be covered here