: Convert strings to here documents in Go (v2) (library)
Here documents allow text files or other data to be embedded in source
files. The heredoc library implements the whitespace filtering and line
break preservation since Go does not have any syntax allowing here
documents
Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu
* Package name: ppx-here
Version : 0.13.0
Upstream Author : Jane Street Group, LLC
* URL : https://github.com/janestreet/ppx_here
* License : MIT
Programming Lang: OCaml
Description : extension
control@ output is the
only one of the mails that they will have received. (Ideally debbugs
would do so itself, but it doesn't, and making our colleagues' lives
easier here is trivial.)
Regards,
Adam
gt; Most certainly not, as network-manager-gnome is not at all involved here.
>
Yeah, that is where the pain is, the spot that needs improvement.
I think we have all been there:
Encounters with a software bug,
feeling the need to report it,
but not knowning _how and where_ to report.
We s
Package: wnpp
Severity: wishlist
Owner: Ilias Tsitsimpis
* Package name: haskell-here
Version : 1.2.11
Upstream Author : Taylor M. Hedberg
* URL : https://hackage.haskell.org/package/here
* License : BSD-3-clause
Programming Lang: Haskell
Description
: https://github.com/MakeNowJust/heredoc
* License : Expat
Programming Lang: Go
Description : Convert strings to here documents in Go
Here documents allow text files or other data to be embedded in source
files. The heredoc library implements the whitespace filtering and line
user specified directories into RAM
Anything-sync-daemon (asd) is a tiny pseudo-daemon designed to
manage user specified directories referred to as sync targets
from here on out, in tmpfs and to periodically sync them back to
the physical disc (HDD/SSD). This is accomplished via a symlinking step
Quoting Henrique de Moraes Holschuh :
On Wed, 21 Sep 2016, john.k...@vfemail.net wrote:
Is the reason for closing the bug 837459 appropriate here? The bug is
still
here and no backported version.
I believe it was appropriately closed, yes.
#837459 is not a request for a backport. Instead
On Wed, 21 Sep 2016, Henrique de Moraes Holschuh wrote:
> for that backport, and refering to bug #836459...
Typo. Make that bug #837459...
--
Henrique Holschuh
On Wed, 21 Sep 2016, john.k...@vfemail.net wrote:
> Is the reason for closing the bug 837459 appropriate here? The bug is still
> here and no backported version.
I believe it was appropriately closed, yes.
#837459 is not a request for a backport. Instead, it is a bug about
something th
On Wed, 21 Sep 2016, john.k...@vfemail.net wrote:
> Is the reason for closing the bug 837459 appropriate here? The bug is still
> here and no backported version.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837459
This bug is fixed in unstable and testing, but is current
Hello,
Is the reason for closing the bug 837459 appropriate here? The bug is still
here and no backported version.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837459
Best wishes,
John
-
ONLY AT VFEmail! - Use our Metadata Mitigator to
et/private/9fans/2015-December/034480.html
> Err sorry I posted link to private list archives.
Here is the link for public list archive. ¹ Sorry for the noise :-)
¹ http://marc.info/?l=9fans&m=144975913529020&w=2
Vasudev Kamath writes:
>
> I think the original message was a troll message :-). I saw the same message
> with similar
> subject on a different list to ¹. So I think you can simply ignore it.
>
> ¹ http://mail.9fans.net/private/9fans/2015-December/034480.html
Err sorry I posted link to private l
02:00 françai s :
>>
>> > Administrators and moderators of ubuntu-devel list, please erase all the
>> > messages that I not should have posted here in debian-devel list.
>> >
>> > I ask this because I probably be in future a good programmer famous and I
>
and moderators of ubuntu-devel list, please erase all the
> > messages that I not should have posted here in debian-devel list.
> >
> > I ask this because I probably be in future a good programmer famous and I
> > do not want to talk about the topics that I should not have pos
ges that I not should have posted here in debian-devel list.
>
> I ask this because I probably be in future a good programmer famous and I
> do not want to talk about the topics that I should not have posted here in
> debian-devel list.
>
> I decided prevent substantial harm to im
Administrators and moderators of ubuntu-devel list, please erase all the
messages that I not should have posted here in debian-devel list.
I ask this because I probably be in future a good programmer famous and I
do not want to talk about the topics that I should not have posted here in
debian
https://www.youtube.com/watch?v=tRvf9LauZIM&list=UUpfKI2v7BTPBrx6HWvEx1Lw
[ Instruments: Analogue Synth: MicroBRUTE & Software Synth Organ: ZynAddSubFX ]
Synth and organ in the cold infinite vastness.
As if abandoned. Seeing bright lights, but feeling no warmth.
Kind of like what old-guard Free/Op
Quoting Marco d'Itri (m...@linux.it):
> On Jul 09, Alessio Treglia wrote:
>
> > I think that it would be valuable for our users to keep the
> > non-default init system working on Jessie for those who do neither
> > intend nor need to switch to systemd.
> I suggest less thinking and more coding th
On Jul 09, Alessio Treglia wrote:
> I think that it would be valuable for our users to keep the
> non-default init system working on Jessie for those who do neither
> intend nor need to switch to systemd.
I suggest less thinking and more coding then, because an updated
systemd-shim still has not
On Fri, Jul 4, 2014 at 3:28 PM, Thorsten Glaser wrote:
>- existing installations of older (pre-jessie) Debian may be
> upgraded to our new standard init system systemd, but only
> after the user has been suitably warned, e.g. via a debconf
> propmpt at priority "medium" (i.e. no
t...@debian.org wrote:
>Steve McIntyre wrote:
>
>>with this constant bickering and sniping. If you must do it, start the
>>GR and see how that goes. I even offer to second it just to help get
>
>Can you help formulate? I do not feel my English skills are
>up to that.
I'm sorry, I don't really have
Le mardi 08 juillet 2014 à 08:13 +0900, Norbert Preining a écrit :
> On Mon, 07 Jul 2014, Josselin Mouette wrote:
> > If they don’t need any of the systemd features, I guess they don’t need
> > any of its reverse dependencies either.
>
> Rubbish. I want network-manager, but I don't want systemd.
Norbert Preining wrote:
>On Mon, 07 Jul 2014, Josselin Mouette wrote:
>> If they donât need any of the systemd features, I guess they donât need
>> any of its reverse dependencies either.
>
>Rubbish. I want network-manager, but I don't want systemd.
I donât, but I want most KDE packages, so
On Mon, 07 Jul 2014, Josselin Mouette wrote:
> If they don’t need any of the systemd features, I guess they don’t need
> any of its reverse dependencies either.
Rubbish. I want network-manager, but I don't want systemd.
NM was working long time without systemd.
Don't spread wrong information.
No
Le vendredi 04 juillet 2014 à 15:09 +0200, Stephan Seitz a écrit :
> But if they don’t want the systemd features why should they write
> software to replace systemd?
If they don’t need any of the systemd features, I guess they don’t need
any of its reverse dependencies either.
So why do they co
me:
>> (I did find his comment funny -- actually, I find the CoC ifself pretty
>> funny --, but I realise that this is an international mailing list and
>> that Austrian-Japanese humour is not necessarily obvious to everyone.)
Tollef Fog Heen:
> Humour [...] does not work very well on large list
The Wanderer dijo [Thu, Jul 03, 2014 at 11:18:12PM -0400]:
> > It must work without systemd well enough to be able to cleanly reboot
> > the system from the GUI, after upgrading.
> >
> > Anything beyond that is nice-to-have, but definitely NOT required.
>
> I, for one, would be highly displeased
* Juliusz Chroboczek [140704 23:00]:
> (I did find his comment funny --
> actually, I find the CoC ifself pretty funny --, but I realise that this
> is an international mailing list and that Austrian-Japanese humour is not
> necessarily obvious to everyone.)
I'd suggest you stop with the country-
On 07/04/2014 10:28 PM, Thorsten Glaser wrote:
> 4) all init systems currently in Debian are supported in jessie;
We don't need a GR to support this option. Of course, all init systems
are supported, to the best of our efforts, and I don't see why someone
would refuse a patch. I haven't seen such
also sprach Stephan Seitz [2014-07-04 15:09
+0200]:
> But if they don’t want the systemd features why should they write
> software to replace systemd?
Because there are better ways to implement it, including more
granular approaches and less of a desktop focus. And you could be
a better upstream
Juliusz Chroboczek writes:
> I'll remind you that this thread started with systemd breaking my
> system, and a systemd maintainer summarily closing my bug report. Not
> once, but twice.
Because the bug was already fixed in a newer version of systemd. While
we're reminding people of things.
>
Hi,
Steve Langasek:
> While I have no interest in joining Norbert in calling for your ban, I would
> like to ask you to consider taking a step back from this thread, and
> evaluating whether such messages are actually contributing to bringing these
> discussions to a conclusion.
>
Thanks for the
Tollef Fog Heen wrote:
> I [...] will try to avoid breaking stuff
I expect no less from a Debian Developer.
> but it's also a use case we don't hit, so breakage there is less likely
> to be seen by us. We'll do our best to fix it when reported, of course.
That is good to hear. It would be eve
> I have yet to find mr Preining funny in any of his mails sent to any of
> the lists I read. Humour, except when accompanied with explicit tags of
> HERE BE HUMOUR does not work very well on large lists.
Well, because I don't write "WARNING HUMOUR COMING" and then
Matthias Urlichs wrote:
>For Zurg (Jessie+1), we're likely to switch to Wayland. How do you plan to
We're *what*?
(Says someone who uses X11 forwarding, VNC in, VNC out, and all
that on an almost-, if not daily, basis.)
OT: prevent-systemd-*_9_all.deb are in my repo. Wookey, feel
free to u
t to any of
the lists I read. Humour, except when accompanied with explicit tags of
HERE BE HUMOUR does not work very well on large lists.
> I have good hope that the systemd maintainers will take this minority
> of users into account in their further development.
I (and I believe I spea
> While I have no interest in joining Norbert in calling for your ban,
Having had the pleasure to meet Norbert in person, I have no doubt that he
was joking when appealing to the CoC. (I did find his comment funny --
actually, I find the CoC ifself pretty funny --, but I realise that this
is an i
Matthias,
On Fri, Jul 04, 2014 at 04:02:38PM +0200, Matthias Urlichs wrote:
> Norbert Preining:
> > > Then shut up and help with the work required to get there,
> > Please stop this inpoliteness, or I request a ban on all mailing lists
> > due to permanent breaking of Code of Conduct.
> *what* Se
* The Wanderer , 2014-07-04, 12:00:
Zurg (Jessie+1),
Has that name actually been formalized in any way?
No. But no worries, if RT chooses a different name, we'll have a GR to
override them. :-P
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
On Jul 04, The Wanderer wrote:
> This part is precisely what I'm objecting to. I don't consider being
> expected to reboot *in order to maintain existing functionality* after
> an upgrade to be reasonable.
Tough luck for you then, I fear that this is a perception issue.
> At the very least, in t
>> forced reboots on a repeated basis, I don't like where this is going.
>>
> systemd and its components can re-exec themselves, that's not the problem.
>
> The problem is that along with systemd we're changing a lot of the
> supporting infrastructure (&qu
d basis, I don't like where this is going.
>
> systemd and its components can re-exec themselves, that's not the problem.
>
> The problem is that along with systemd we're changing a lot of the
> supporting infrastructure ("we" here is Upstream, for the
e-exec themselves, that's not the problem.
The problem is that along with systemd we're changing a lot of the
supporting infrastructure ("we" here is Upstream, for the most part).
Keeping old low-level interfaces around just to avoid logging out or
rebooting may or may not be s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/04/2014 10:42 AM, Adam Borowski wrote:
> On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote:
>
>> So, let me get this straight:
>>
>> You're saying that if, having decided to postpone rebooting after
>> an upgrade where any reasona
On Fri, Jul 4, 2014, at 16:42, Adam Borowski wrote:
> On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote:
> > So, let me get this straight:
> >
> > You're saying that if, having decided to postpone rebooting after an
> > upgrade where any reasonable person would expect to reboot
>
> Thi
On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote:
> So, let me get this straight:
>
> You're saying that if, having decided to postpone rebooting after an
> upgrade where any reasonable person would expect to reboot
This is Debian, not Windows or Red Hat, forced reboots are not accept
Steve McIntyre wrote:
>with this constant bickering and sniping. If you must do it, start the
>GR and see how that goes. I even offer to second it just to help get
Can you help formulate? I do not feel my English skills are
up to that.
Also, what options do we need?
1) systemd is the only init
Hi,
Norbert Preining:
> > Then shut up and help with the work required to get there,
> Please stop this inpoliteness, or I request a ban on all mailing lists
> due to permanent breaking of Code of Conduct.
*what* Seriously?!?
One of us seems to harbor a severe misconception or two about what kin
it.
In SYSV init, I can just use "set -x". That just rocks.
(But anyway, I do not wish to discuss this here - there
are more suitable places/threads.)
>> systemd is a backdoor in that, by means of vendor lock-in
>
>Which vendor are you talking about, exactly?
"vendor lock-
Thorsten Glaser wrote:
>
>You know, backdoors are not only code vulnerabilities.
>
>systemd is a backdoor in that, like the availability of Steam
>games for DDs, it has a chance to hinder the progress of all
>projects done in the spare time of the people affected.
Thorsten, you're too late. The ar
On Fri, 04 Jul 2014, Matthias Urlichs wrote:
> Then shut up and help with the work required to get there,
Please stop this inpoliteness, or I request a ban on all mailing lists
due to permanent breaking of Code of Conduct.
(Long live the CoC - I am *so* happy to have it!! - hope someone
got
On Thu, Jul 03, 2014 at 08:40:59PM +0200, Matthias Urlichs wrote:
The problem is that some people bitch endlessly abut how evil systemd is
_instead_of_ producing software (not just patches) to replace what systemd
offers.
But if they don’t want the systemd features why should they write
softwa
Hi Thorsten,
while I tend to basically acknowledge your points here, there is still one
thing you obviously did not get until now, if I followed along correctly.
>For example, systemd has support for its own (S)NTP client, but also
>supports xntpd (rudely leaving OpenNTPD out already
Dominik George dixit:
>systemd, in its nature as an init system, starts what you tell it to
>start. There is nothing that can prevent it from starting openntpd if
>you want that. If you through a service file at it, or even an LSB
>init script, then systemd has no choice but to start it.
No, this
Juliusz Chroboczek wrote:
>> The problem is that some people bitch endlessly abut how evil systemd is
>> _instead_of_ producing software (not just patches) to replace what
>> systemd offers.
>
>Abstracting away from your somewhat offensive choice of language, that's
>a good point. As far as I'm aw
Hi,
Thorsten Glaser:
> systemd is a backdoor in that, like the availability of Steam
> games for DDs, it has a chance to hinder the progress of all
> projects done in the spare time of the people affected.
>
Yeah. It "has a chance".
It also "has a chance" to give people a big chunk of spare time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/04/2014 04:52 AM, Philip Hands wrote:
> The Wanderer writes:
>
>> ... particularly because I use rather fewer things than many other
>> people, and don't use most fancy GUI elements. (For example, I
>> don't have a graphical "power button" a
> The problem is that some people bitch endlessly abut how evil systemd is
> _instead_of_ producing software (not just patches) to replace what
> systemd offers.
Abstracting away from your somewhat offensive choice of language, that's
a good point. As far as I'm aware, the only major distribution
OdyX wrote:
>all means, go for it. That said, as far as I remember, the latest GR
>proposal [4] on this subject failed to gather the mandatory K seconds
>though. For me, this indicates that not even K=5 DDs were interested in
I was not even aware of that proposal. This may also indicate lack
of,
In other news for Thu, Jul 03, 2014 at 04:59:25PM +0200, Thorsten Glaser has
been seen typing:
> No, there just has not been any challenge that met the form and
> other requirements… and I am at a bit of loss at what to do here.
> Besides, it’s not that the TC made a decision. Rathe
k that
> No, there just has not been any challenge that met the form and
> other requirements… and I am at a bit of loss at what to do here.
>
> Besides, it’s not that the TC made a decision. Rather, the TC was
> split, and the chairman threw in his weight.
Sorry, but this is
On Thu, Jul 3, 2014, at 16:59, Thorsten Glaser wrote:
> Besides, it’s not that the TC made a decision. Rather, the TC was
> split, and the chairman threw in his weight. This is absolutely not
> what I’d call a project(!) decision.
No! The TC has made the decision with full adherence to Debian
Con
The Wanderer writes:
> ... particularly because I use rather fewer things than
> many other people, and don't use most fancy GUI elements. (For example,
> I don't have a graphical "power button" at all; I shut down by exiting
> my window manager, logging out of the console where I had originally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/03/2014 11:53 PM, Russ Allbery wrote:
> The Wanderer writes:
>
>> I, for one, would be highly displeased if a routine dist-upgrade to
>> testing required me to reboot to avoid having things break.
>
>> I generally dist-upgrade my primary co
Hi,
The Wanderer:
> I, for one, would be highly displeased if a routine dist-upgrade to
> testing required me to reboot to avoid having things break.
>
We're talking about an upgrade from one release to the other here,
with many intrusive changes (not just systemd).
If you do th
The Wanderer writes:
> I, for one, would be highly displeased if a routine dist-upgrade to
> testing required me to reboot to avoid having things break.
> I generally dist-upgrade my primary computer to testing about once a
> week, give or take, but I don't reboot it more often than once a month
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/03/2014 01:40 PM, Matthias Urlichs wrote:
> Hi,
>
> Thorsten Glaser:
>>> Can we get over this now and start making Jessie the most awesome
>>> stable release we've ever prepared together?
>>
>> To do that, it MUST work without systemd, if a
On 03/07/14 22:50, David Weinehall wrote:
> Why would the NSA take even the slightest risk of discovery
> when they could put a backdoor in a driver for a piece of hardware that
> has full access to your system?
Or on the firmware of your HDD/SDD:
http://s3.eurecom.fr/~zaddach/docs/Recon14_HDD.pd
Hi,
Matthias Urlichs writes:
>> Please respect our decision to stay away from systemd and still be
>> Debian users. If possible, please, don't resist changes that make our
>> lives easier.
>>
> *Sigh*.
>
> The problem is not that anybody resists such changes.
I disagree. People *do* in fact res
On Thu, Jul 03, 2014 at 11:25:36AM -0700, Russ Allbery wrote:
[snip]
> If the NSA are going to hide back-doors in open source projects (a rather
> dubious idea to start with, given how difficult it is and how much social
> blowback there would be when such a thing was inevitably discovered), they
>
systemd
offers.
> For thou art so possessed with murderous hate,
Three words do come to mind … which I'll not write down here,
in order not to escalate this discussion.
You may mail me your guesses privately. ;-)
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-devel-r
Alexander Pushkin writes:
> For some of us there will never be an awesome Debian release that at
> it's core contains systemd. It's core developers, Lennart Poettering and
> Kay Sievers, work for a company that has multi-billion dollar contracts
> with NSA. It is your choice to assume good faith
Didier, Hello.
> The proper solution is to stop trying to hide ourselves from to the fact
> that some sort of systemd interfaces have been made unavoidable in
> modern desktop environments (fact which is rightfully reflected in our
> dependencies tree).
> Can we get over this now and start ma
Hi,
Thorsten Glaser:
> A lot of Debian systems even run without dbus!
>
Yeah. So? systemd doesn't force you to run a dbus daemon.
> No, there just has not been any challenge that met the form and
> other requirements… and I am at a bit of loss at what to do here.
>
You get
technical committee has made a
> decision which stayed unchallenged (so far), I've now come to think that
No, there just has not been any challenge that met the form and
other requirements… and I am at a bit of loss at what to do here.
Besides, it’s not that the TC made a decision. Rather
modern desktop environments (fact which is rightfully reflected in our
dependencies tree). Many of the interfaces of systemd are here to stay
and will make their way through our stack (like it or not); fact is they
already made it quite far in at least Gnome and KDE.
As developers of Debian (which t
View this message in a browser.
http://archives.subscribermail.com/msg/e06249d1cc5c4fa4a8bceb6f30de375e.htm
To view this message in a browser. Copy and Paste the following URL in your web
address bar: http://www.spacecoastharley.com/default.asp?page=e-blast
taozhijiang writes:
> I want to using #define / #undef, and want to put them in a single
> macro, some thing like:
> #define DECALRE_TYPE(type) \
> { #undef __curr_type; #define _curr_type type; }
> as we know, this can not passed with CPP, but I need this logical here.
I'
, this can not passed with CPP, but I need this logical here.
Generally, the problem comes from
#define ser_field(type, var) \
ser_new_field(tra, #type, #var, offsetof(struct_type, var))
I do not want another additional parameter in this macro like
#define ser_field(type,var,struct_type), and I
brary to develop API-to-LV2 bridges
NASPRO Bridge it is a little helper library to develop insert-your-API-here
to LV2 bridges.
.
As of now, it basically offers a few utility functions and Turtle/RDF
serialization for LV2 dynamic manifest generation, supporting the
following LV2 specifica
Hi All,
urgently need poker links. interested please do not hesitate to contact me
back
Jon Peter
I'm having exactly the same problem here with udev 0.125-7 on a
Testing...
If there is any info/test I could do to help fixing that bug, just ask.
btw, this bug should have its severity set to "grave" or even "critical",
as it prevents the system from working properly:
Programming Lang: Perl
Description : install files from here to there
ExtUtils::Install handles the installing and uninstalling of perl modules,
scripts,
man pages, etc.
.
The module is also bundled with the Perl core in the perl-modules package,
but a separately packaged newer version is required
7 hobbies of highly effective people
You know you are cool when your boss asks you about that thing on your watch
that tells time. http://www.retueiag.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I’m doing the same but with a different company
Anyway to help me with referrals for my referral link?
http://laptops.freepay.com/?r=43388891
Be a better friend, newshound, and
know-it-all with Yahoo!
Before plugging in devices:
$ find /proc/bus/usb
/proc/bus/usb
/proc/bus/usb/004
/proc/bus/usb/004/001
/proc/bus/usb/003
/proc/bus/usb/003/002
/proc/bus/usb/003/001
/proc/bus/usb/002
/proc/bus/usb/002/001
/proc/bus/usb/001
/proc/bus/usb/001/005
/proc/bus/usb/001/004
/proc/bus/usb/001/001
/proc/bus
a blockbuster trial and other things
that you can cancel and never get billed for. Anyways, if you want to check it
out, here is the link: http://www.notebooks4free.com/default.aspx?r=783924
company doesn't scam or anything, the catch: I need 20 referrals to sign up
with my link and Co
71798
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e MAIL FROM + SENDER IP, which a good
trade off for alioth, but may not be true for DD accounts. that's the
sole "deviation" of what has been discussed here, and is not very
relevant to the discussion anyway.
Technically, I don't know what you want me to say more than what is
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> For the record (it was already said in the thread IIRC), the setup we
> are discussing is in production on alioth since sth like 4 or 5 monthes
> now (maybe a bit less) on my idea, and thanks to Raphael Hertzog for
> actually using his alioth admin
Le mar 18 juillet 2006 13:20, Adrian von Bidder a écrit :
> Apart from the fact that the opinions seem to be set (and haven't
> really changed since the last time the discussion came up IIRC, so we
> really can stop arguing - nothing new for quite some time...): am I
> correct in my observation tha
Apart from the fact that the opinions seem to be set (and haven't really
changed since the last time the discussion came up IIRC, so we really can
stop arguing - nothing new for quite some time...): am I correct in my
observation that nobody who has participated in this discussion up to now
is
On 6/20/06, Michael Banck <[EMAIL PROTECTED]> wrote:
On Tue, Jun 20, 2006 at 11:37:22AM +0200, Olaf van der Spek wrote:
> How are others supposed to be aware of that if you don't tell them?
Uhm, did you read the thread you're replying to? Or are you just
rehashing the complaints over and over a
On Tue, Jun 20, 2006 at 11:37:22AM +0200, Olaf van der Spek wrote:
> How are others supposed to be aware of that if you don't tell them?
Uhm, did you read the thread you're replying to? Or are you just
rehashing the complaints over and over again to get more attention?
Michael
--
Michael Banc
On 6/20/06, Tollef Fog Heen <[EMAIL PROTECTED]> wrote:
* Marc Haber
| On Sun, 18 Jun 2006 07:51:04 +0200, Tollef Fog Heen <[EMAIL PROTECTED]>
| wrote:
| >Useful patches and comments are always welcome.
|
| The apache maintainers' "reaction" to #349716, #349709, #349708 and
| #366124 (the latter
* Marc Haber
| On Sun, 18 Jun 2006 07:51:04 +0200, Tollef Fog Heen <[EMAIL PROTECTED]>
| wrote:
| >Useful patches and comments are always welcome.
|
| The apache maintainers' "reaction" to #349716, #349709, #349708 and
| #366124 (the latter one a possible security issue), is very
| discouraging
On Sun, 18 Jun 2006 07:51:04 +0200, Tollef Fog Heen <[EMAIL PROTECTED]>
wrote:
>Useful patches and comments are always welcome.
The apache maintainers' "reaction" to #349716, #349709, #349708 and
#366124 (the latter one a possible security issue), is very
discouraging to comment and to submit patc
Hi
Tollef Fog Heen wrote:
Adrian von Bidder skrev:
On Thursday 15 June 2006 16:06, Marc Chantreux wrote:
Is there a way to help/join/"have news from" the apache team ?
Have you tried contacting the apache maintainers directly? (I'd cc
such mails to the [EMAIL PROTECTED] list, just for the
1 - 100 of 181 matches
Mail list logo
