search for: headsup

Displaying 20 results from an estimated 54 matches for "headsup".

2020 Mar 18
0
[Dovecot-news] Headsup on feature removal
On 17/03/20 7:50 pm, Aki Tuomi wrote: > Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. > > We are starting to gradually remove some of these parts, which are unused, untested or deprecated. > We will provide advance notification before removing anything. > > To start, the following
2020 Mar 18
0
Headsup on feature removal - password
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 18/03/2020 00:06 Rupert Gallagher <ruga@protonmail.com> wrote: </div> <div> <br> </div> <div> <br>
2020 Mar 18
2
Headsup on feature removal - password
Was there any reason for this message to be HTML-only? On Wed, Mar 18, 2020 at 07:13:12AM +0200, Aki Tuomi wrote: > <!doctype html> > <html> > <head> > <meta charset="UTF-8"> > </head> > <body> > <div> > <br> > </div> > <blockquote type="cite"> > <div> >
2020 Mar 18
0
Headsup on feature removal - password
On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: >Was there any reason for this message to be HTML-only? Was there any reason to 'top post' and include the HTML text? -- Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL:
2020 Mar 18
2
Headsup on feature removal - password
On Wed, Mar 18, 2020 at 10:38:37AM -0400, Jerry wrote: > On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: > >Was there any reason for this message to be HTML-only? > > Was there any reason to 'top post' and include the HTML text? Yes. (1) To indicate that my question was about the whole message and not its contents. I normally don't top-post. (2) To make it
2020 Mar 18
0
Headsup on feature removal - password
> On 18/03/2020 17:31 Hendrik Boom <hendrik at topoi.pooq.com> wrote: > > > On Wed, Mar 18, 2020 at 10:38:37AM -0400, Jerry wrote: > > On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: > > >Was there any reason for this message to be HTML-only? > > > > Was there any reason to 'top post' and include the HTML text? > > Yes. >
2020 Mar 18
2
[Dovecot-news] Headsup on feature removal
18.03.20, 04:32 CET, Peter: > Please consider holding off on removing features for the next major > release, 2.4.0 instead. It makes sense to retain, in as much as is > possible, feature backwards compatibility across a major release. Seconded! That you are going to drop features from the code base that are old and rarely used is understandable. Doing so in a minor release is not.
2020 Mar 18
0
[Dovecot-news] Headsup on feature removal
I fully agree with this: > Please consider holding off on removing features for the next major > release, 2.4.0 instead. It makes sense to retain, in as much as is > possible, feature backwards compatibility across a major release.
2020 Mar 19
0
Headsup on feature removal
>>>>> "Alessio" == Alessio Cecchi <alessio at skye.it> writes: Alessio> Hi Aki and Remo, Alessio> switch from vpopmail driver to SQL driver (if you are using vpopmail with mysql as backend) is Alessio> very simple. Alessio> First you need to setup the right query for vpopmail database: Alessio> # cat /etc/dovecot/dovecot-sql.conf.ext Alessio>
2020 Mar 19
0
[Dovecot-news] Headsup on feature removal
On 18-03-2020 22:55, Noel Butler wrote: > On 19/03/2020 03:56, JAVIER MIGUEL RODRIGUEZ wrote: > >> I fully agree with this: >> >>> Please consider holding off on removing features for the next major >>> release, 2.4.0 instead. ?It makes sense to retain, in as much as is >>> possible, feature backwards compatibility across a major release. >>
2005 Feb 20
0
HeadsUp: will be moving list and RoR next week
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Everyone, Want to let you know that I''ll be syncing over all the aspects of RoR''s mailing lists and it''s site onto a new dedicated server that''ll just be for RubyOnRails.org/.com. It''ll all be seemless and kept in sync until David flips the DNS switch, but there will be a couple of times where the
2003 Mar 31
1
HEADSUP: XFree86 4.3.0 update
On Tue, 18 Mar 2003 11:55, Daniel O'Connor wrote: > On Tue, 2003-03-18 at 02:54, Fred Clift wrote: > This is interesting because I had a crash with Mozilla which only > stopped when I built WITHOUT_XFT. > > I have updated fontconfig, freetype etc.. with no luck :( Not sure I replied to this but.. The solution was that I had a font directory X knew about but not fontconfig :(
2003 Aug 06
0
HEADSUP: USB da(4) quirks deprecated
I have committed code to disable the USB quirks in da(4). Since we now have code that should handle the common case of a failure after receiving 6 byte commands, most of them should no longer be necessary. However, the only way to tell if a quirk is really needed is to test the new code with the quirks disabled. You may have a device (USB camera, pen drive, hard drive, ...) that begins to get
2003 Aug 18
1
HEADSUP: apm(4) driver synced with current
In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated
2010 Feb 15
2
[HEADSUP]: ports feature freeze now in effect
In preparation for 7.3-RELEASE, the ports tree is now in feature freeze. Normal upgrade, new ports, and changes that only affect other branches are allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commts to ports with unusually high number of dependent ports,
2020 Mar 19
2
Headsup on feature removal
Il 19/03/20 02:01, John Stoffel ha scritto: > Alessio> ### user_query for vpopmail > Alessio> user_query = SELECT pw_dir AS home, 89 AS uid, 89 AS gid, > Alessio> concat('*:backend=', pw_shell) AS quota_rule FROM vpopmail > Alessio> WHERE pw_name = '%n' AND pw_domain = '%d' > > Careful! You need to explain that 89 is the UID and GID of the
2020 Mar 17
0
Headsup on feature removal
With these planned changes, you mention they will be removed from 'core', so is the intention to allow more of these legacy plugins to more to their own repo's for those that might still want to use them? Eg, more in the the path of plug-in architecture? Just curious for clarity. Oh, and have to add.. still waiting on the variable capability patch, to allow plugins to modify
2020 Mar 18
0
Headsup on feature removal
Amongst other plug-ins, yes.. On 2020-03-17 10:15 p.m., Aki Tuomi wrote: > Those plugins can be resurrected with simple `git revert`. > > Are you planning on open sourcing your client id authetication plugin? > > Aki >> On 18/03/2020 01:44 Michael Peddemors < michael at linuxmagic.com >> <mailto:michael at linuxmagic.com>> wrote: >> >>
2010 Jul 05
1
[LLVMdev] [HEADSUP] Another attempt at CallInst operand rotation
Reminder... Round one has been committed as <http://llvm.org/viewvc/llvm-project?view=rev&revision=107432> I hope that it got digested by now, as I plan to commit the second round tomorrow. In fact I made two test commits already: r107480 and r107580, the former of which actually uncovered some more uses of the low-level interfaces in core LLVM that have slipped through. To be
2020 Mar 18
0
Headsup on feature removal
Hi! I understand that it is not trivial to move away from vpopmail and does require changing a working system. But then again, one should be able to configure MySQL passdb/userdb with vpopmail schema. I am not familiar with vpopmail but if someone comes with instructions we can polish them a bit (if necessary) and publish them as howto on doc.dovecot.org. Aki > On 18/03/2020 17:52 Remo