From linuxhippy at gmail.com Fri May 2 10:49:23 2008 From: linuxhippy at gmail.com (Clemens Eisserer) Date: Fri, 2 May 2008 19:49:23 +0200 Subject: Admin-Account for forums.java.net Message-ID: <194f62550805021049q17d7cae6p31fb72a4767d0e32@mail.gmail.com> Hello, I know this is completly off-topic, but I don't know of any better place to ask this. The forums at forums.java.net seem to be spammed a lot. I understand that there are little resources left to pay moderators, but wouldn't it be possible for me to get a moderator role. Its just annoying to see the tons of advertising there, I would not take the time to search for it but I regulary visit it for years now, and if I see one I could simply delete it. Do you know any better place to ask for such rights? Thanks, lg Clemens From Jeff.Dinkins at Sun.COM Fri May 2 10:51:02 2008 From: Jeff.Dinkins at Sun.COM (Jeff Dinkins) Date: Fri, 02 May 2008 10:51:02 -0700 Subject: Admin-Account for forums.java.net In-Reply-To: <194f62550805021049q17d7cae6p31fb72a4767d0e32@mail.gmail.com> References: <194f62550805021049q17d7cae6p31fb72a4767d0e32@mail.gmail.com> Message-ID: <94A1EA66-6E4A-4783-8019-7F8C95BB2D64@sun.com> Hi - I'll plug you into the right people. jeff On May 2, 2008, at 10:49 AM, Clemens Eisserer wrote: > Hello, > > I know this is completly off-topic, but I don't know of any better > place to ask this. > The forums at forums.java.net seem to be spammed a lot. > > I understand that there are little resources left to pay moderators, > but wouldn't it be possible for me to get a moderator role. > Its just annoying to see the tons of advertising there, I would not > take the time to search for it but I regulary visit it for years now, > and if I see one I could simply delete it. > > Do you know any better place to ask for such rights? > > Thanks, lg Clemens From mark at klomp.org Thu May 29 14:31:46 2008 From: mark at klomp.org (Mark Wielaard) Date: Thu, 29 May 2008 23:31:46 +0200 Subject: Mercurial mail flood Message-ID: <1212096706.619.23.camel@dijkstra.wildebeest.org> Hi all, That mercurial mail flood on distro-pkg-dev was the result of Andrew's hard work merging all the icedtea6 changes into icedtea[7] and upgrading to openjdk b26. Apologies for not realizing in time that this would replay all of the history (since February!) and generated 287 emails (urgh). [*] I'll try and change the scripts so they bundle the commits of one push. This is what some other openjdk mailinglists seem to do. Although the actual patches are lost then from the email. Are the mercurial scripts for those other lists available somewhere? Thanks and sorry for the spamming, Mark [*] Currently we use: [hooks] incoming.notify = python:hgext.notify.hook [notify] sources = serve push pull bundle test = False maxdiff = 500 [usersubs] ## key is subscriber email, value is comma-separated list of glob patterns # We don't want notification of /hg/testrepo, so not included. openjdk # overrides maxdiff to not send any diffs. The others use the default above. distro-pkg-dev at openjdk.java.net = /hg/fedora,/hg/icedtea,/hg/icedtea6,/hg/openjdk,/hg/icepick,/hg/brandweg From martinrb at google.com Thu May 29 14:51:40 2008 From: martinrb at google.com (Martin Buchholz) Date: Thu, 29 May 2008 14:51:40 -0700 Subject: jre download bundles don't extract executably Message-ID: <1ccfd1c10805291451x75e6548fneed7ea6bfff954d6@mail.gmail.com> HI guys, I downloaded some of the JREs from download.java.net. The JRE's are packaged differently from the JDKs, for no apparent reason. The JDKs are .bin files. The JREs are .jar files. Why? The JDK 6 download bundles were all .bin files. When I extract the JREs (using java -jar ) The resulting jre1.7.0 directory contains no executable files. For example, here's what happens when I try to run "java": $ bin/java -version zsh: permission denied: bin/java Martin From Tim.Bell at Sun.COM Thu May 29 15:17:07 2008 From: Tim.Bell at Sun.COM (Tim Bell) Date: Thu, 29 May 2008 15:17:07 -0700 Subject: jre download bundles don't extract executably In-Reply-To: <1ccfd1c10805291451x75e6548fneed7ea6bfff954d6@mail.gmail.com> References: <1ccfd1c10805291451x75e6548fneed7ea6bfff954d6@mail.gmail.com> Message-ID: <483F2B63.9090408@sun.com> Hi Martin > I downloaded some of the JREs from download.java.net. > The JRE's are packaged differently from the JDKs, for no apparent reason. > The JDKs are .bin files. The JREs are .jar files. Why? I don't know the reasoning behind this new bundling. I tried to dig up the Bug-ID where these packaging changes went in, but have not found it yet. > The JDK 6 download bundles were all .bin files. > > When I extract the JREs (using java -jar ) > The resulting jre1.7.0 directory contains no executable files. See Bug-ID 6385672 "JRE installer fails to set executable attribute on Linux" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6385672 The evaluation on 6385672 seems to indicate these click-wrap .jar installers have been built for a long time, but were not released. Maybe that decision changed recently. I will ask some questions. HTH - Tim From mr at sun.com Thu May 29 21:05:13 2008 From: mr at sun.com (Mark Reinhold) Date: Thu, 29 May 2008 21:05:13 -0700 Subject: Mercurial mail flood In-Reply-To: mark@klomp.org; Thu, 29 May 2008 23:31:46 +0200; <1212096706.619.23.camel@dijkstra.wildebeest.org> Message-ID: <20080530040513.437452558@callebaut.niobe.net> > Date: Thu, 29 May 2008 23:31:46 +0200 > From: Mark Wielaard > That mercurial mail flood on distro-pkg-dev was the result of Andrew's > hard work merging all the icedtea6 changes into icedtea[7] and upgrading > to openjdk b26. Apologies for not realizing in time that this would > replay all of the history (since February!) and generated 287 emails > (urgh). [*] Nice work, but yeah -- that was an awful lot of email ... > I'll try and change the scripts so they bundle the commits of one push. > This is what some other openjdk mailinglists seem to do. Although the > actual patches are lost then from the email. Are the mercurial scripts > for those other lists available somewhere? We're using a custom notify script for the OpenJDK repositories. We can't publish it just yet -- it's in the same lawyer-wait state as the jcheck extension. (I expect that to be resolved in, at most, the next six weeks.) Personally I view the inclusion of patches in Mercurial notifications as a distraction unless they're very short, but I know that opinions differ on this. - Mark From mark at klomp.org Fri May 30 05:06:56 2008 From: mark at klomp.org (Mark Wielaard) Date: Fri, 30 May 2008 14:06:56 +0200 Subject: Mercurial mail flood In-Reply-To: <17c6771e0805300443s2dd969d1q9363c56879581b4f@mail.gmail.com> References: <1212096706.619.23.camel@dijkstra.wildebeest.org> <20080530040513.437452558@callebaut.niobe.net> <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> <483FDC4A.7090302@ubuntu.com> <17c6771e0805300443s2dd969d1q9363c56879581b4f@mail.gmail.com> Message-ID: <1212149216.619.41.camel@dijkstra.wildebeest.org> Hi, On Fri, 2008-05-30 at 12:43 +0100, Andrew John Hughes wrote: > 2008/5/30 Matthias Klose : > > > > Could we establish a policy not to redirect the commit messages to the ML, but > > instead require a manual posting of a patch (excluding generated files), > > together with a short rationale why the patch is applied and what it is supposed > > to fix? Should make it easier to track the history of patches. This information > > might be in some bug tracker, but probably not in the IcedTea tracker. Having > > this information in one place on the ML would be helpful. > > +1 It seems a good policy (especially the excluding generated files part) IF this is done for all patches/commits, even those which some might find trivial. The reason I like having the commit messages including the actual patches is because only then do I really have a good overview of what is going into the tree. If people would actually post each and every patch that they commit then that would obviously be enough. And we could then use the rss feed to track and match posted patches to what actually goes in. For those hating rss and having to be always online (like me) we could install rss2email. Cheers, Mark From Jonathan.Gibbons at Sun.COM Fri May 30 06:53:30 2008 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 30 May 2008 06:53:30 -0700 Subject: Mercurial mail flood In-Reply-To: <1212149216.619.41.camel@dijkstra.wildebeest.org> References: <1212096706.619.23.camel@dijkstra.wildebeest.org> <20080530040513.437452558@callebaut.niobe.net> <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> <483FDC4A.7090302@ubuntu.com> <17c6771e0805300443s2dd969d1q9363c56879581b4f@mail.gmail.com> <1212149216.619.41.camel@dijkstra.wildebeest.org> Message-ID: For my part, I dislike the messages going to all the -dev aliases for an integration area if only because it clogs up the mail archives. When I put back changes to TL, the same announcement goes to 4 separate mailing lists, including 3 -dev aliases, and is archived in each of those mail archives. I know disk is cheap, but .... I still think that this would be better with either RSS or mail to a list that is specific to an integration area. -- Jon On May 30, 2008, at 5:06 AM, Mark Wielaard wrote: > Hi, > > On Fri, 2008-05-30 at 12:43 +0100, Andrew John Hughes wrote: >> 2008/5/30 Matthias Klose : >>> >>> Could we establish a policy not to redirect the commit messages to >>> the ML, but >>> instead require a manual posting of a patch (excluding generated >>> files), >>> together with a short rationale why the patch is applied and what >>> it is supposed >>> to fix? Should make it easier to track the history of patches. >>> This information >>> might be in some bug tracker, but probably not in the IcedTea >>> tracker. Having >>> this information in one place on the ML would be helpful. >> >> +1 > > It seems a good policy (especially the excluding generated files part) > IF this is done for all patches/commits, even those which some might > find trivial. > > The reason I like having the commit messages including the actual > patches is because only then do I really have a good overview of > what is > going into the tree. If people would actually post each and every > patch > that they commit then that would obviously be enough. > > And we could then use the rss feed to track and match posted patches > to > what actually goes in. For those hating rss and having to be always > online (like me) we could install rss2email. > > Cheers, > > Mark > From doko at ubuntu.com Fri May 30 03:51:54 2008 From: doko at ubuntu.com (Matthias Klose) Date: Fri, 30 May 2008 12:51:54 +0200 Subject: Mercurial mail flood In-Reply-To: <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> References: <1212096706.619.23.camel@dijkstra.wildebeest.org> <20080530040513.437452558@callebaut.niobe.net> <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> Message-ID: <483FDC4A.7090302@ubuntu.com> Andrew John Hughes schrieb: > 2008/5/30 Mark Reinhold : >> Personally I view the inclusion of patches in Mercurial notifications as >> a distraction unless they're very short, but I know that opinions differ >> on this. >> >> - Mark >> > > Well, for me, it depends on whether the patches have been published on > a list prior to the commit. > With Classpath, we've never had patches in the mails; the commit > message and links to the diffs > on CVS appears. The patches are posted separately to a separate list. > In contrast, I've found some > of the icedtea commits useful to read, because that's the only place > I've seen the change. But these > seem to be truncated if they go over a certain length and generated > files in the repository isn't helping > this. So I'd tend to agree that very short easily digestable ones are > fine in the commits (see Lillian's recent minor > IcedTea changes for the release) but that larger patches should be > attached in a separate mail and (dare I say it) on a > separate list. Could we establish a policy not to redirect the commit messages to the ML, but instead require a manual posting of a patch (excluding generated files), together with a short rationale why the patch is applied and what it is supposed to fix? Should make it easier to track the history of patches. This information might be in some bug tracker, but probably not in the IcedTea tracker. Having this information in one place on the ML would be helpful. Matthias From roman at kennke.org Fri May 30 04:02:56 2008 From: roman at kennke.org (Roman Kennke) Date: Fri, 30 May 2008 13:02:56 +0200 Subject: Mercurial mail flood In-Reply-To: <483FDC4A.7090302@ubuntu.com> References: <1212096706.619.23.camel@dijkstra.wildebeest.org> <20080530040513.437452558@callebaut.niobe.net> <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> <483FDC4A.7090302@ubuntu.com> Message-ID: <1212145376.6702.35.camel@moonlight> Hi there, > Could we establish a policy not to redirect the commit messages to the > ML, My point of view is that none of these should be sent to the lists, who is interested in reading all the commit messages can subscribe to the RSS feed, for example: http://icedtea.classpath.org/hg/icedtea/rss-log Same for the other -dev lists (althougt, they don't have so much HG related traffic, probably because they don't post single commits, but aggregate everything from a push (or so). /Roman -- http://kennke.org/blog/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil Url : http://mail.openjdk.java.net/pipermail/web-discuss/attachments/20080530/7bc0ef25/attachment.bin From gnu_andrew at member.fsf.org Fri May 30 04:43:32 2008 From: gnu_andrew at member.fsf.org (Andrew John Hughes) Date: Fri, 30 May 2008 12:43:32 +0100 Subject: Mercurial mail flood In-Reply-To: <483FDC4A.7090302@ubuntu.com> References: <1212096706.619.23.camel@dijkstra.wildebeest.org> <20080530040513.437452558@callebaut.niobe.net> <17c6771e0805300103n69f6e799lbd3ee73c10470765@mail.gmail.com> <483FDC4A.7090302@ubuntu.com> Message-ID: <17c6771e0805300443s2dd969d1q9363c56879581b4f@mail.gmail.com> 2008/5/30 Matthias Klose : > Andrew John Hughes schrieb: >> 2008/5/30 Mark Reinhold : >>> Personally I view the inclusion of patches in Mercurial notifications as >>> a distraction unless they're very short, but I know that opinions differ >>> on this. >>> >>> - Mark >>> >> >> Well, for me, it depends on whether the patches have been published on >> a list prior to the commit. >> With Classpath, we've never had patches in the mails; the commit >> message and links to the diffs >> on CVS appears. The patches are posted separately to a separate list. >> In contrast, I've found some >> of the icedtea commits useful to read, because that's the only place >> I've seen the change. But these >> seem to be truncated if they go over a certain length and generated >> files in the repository isn't helping >> this. So I'd tend to agree that very short easily digestable ones are >> fine in the commits (see Lillian's recent minor >> IcedTea changes for the release) but that larger patches should be >> attached in a separate mail and (dare I say it) on a >> separate list. > > Could we establish a policy not to redirect the commit messages to the ML, but > instead require a manual posting of a patch (excluding generated files), > together with a short rationale why the patch is applied and what it is supposed > to fix? Should make it easier to track the history of patches. This information > might be in some bug tracker, but probably not in the IcedTea tracker. Having > this information in one place on the ML would be helpful. > > Matthias > +1 -- Andrew :-) Support Free Java! Contribute to GNU Classpath and the OpenJDK http://www.gnu.org/software/classpath http://openjdk.java.net PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8