* bug#21191: Obsolete eudcb-ph.el
@ 2015-08-05 6:53 Glenn Morris
2015-08-06 6:38 ` Thomas Fitzsimmons
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2015-08-05 6:53 UTC (permalink / raw)
To: 21191; +Cc: fitzsim
Package: emacs
Version: 24.5
Severity: wishlist
I doubt CCSO PH/QI has seen much/any use in at least the past decade,
so I suggest obsoleting eudcb-ph.el (and making eudc basically an ldap
client. Well, I see there's also bbdb and a never-documented or
announced AddressBook backend.)
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#21191: Obsolete eudcb-ph.el
2015-08-05 6:53 bug#21191: Obsolete eudcb-ph.el Glenn Morris
@ 2015-08-06 6:38 ` Thomas Fitzsimmons
2015-08-12 6:02 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Fitzsimmons @ 2015-08-06 6:38 UTC (permalink / raw)
To: Glenn Morris; +Cc: 21191
Glenn Morris <rgm@gnu.org> writes:
> Package: emacs
> Version: 24.5
> Severity: wishlist
>
> I doubt CCSO PH/QI has seen much/any use in at least the past decade,
> so I suggest obsoleting eudcb-ph.el
Makes sense. I'll work on this. I didn't see a specific set of
instructions in admin or CONTRIBUTE for how to obsolete an elisp file,
so I'll try to follow the procedures that were used for some other
recently-obsoleted files.
I also noticed eudcb-bob.el; I'm not sure what it does or if anyone uses
it. Any thoughts on that one?
> (and making eudc basically an ldap client. Well, I see there's also
> bbdb and a never-documented or announced AddressBook backend.)
I'll try to add a section to the Info manual for eudcb-mab.el.
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#21191: Obsolete eudcb-ph.el
2015-08-06 6:38 ` Thomas Fitzsimmons
@ 2015-08-12 6:02 ` Glenn Morris
2015-12-07 3:04 ` Thomas Fitzsimmons
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2015-08-12 6:02 UTC (permalink / raw)
To: Thomas Fitzsimmons; +Cc: 21191
Thomas Fitzsimmons wrote:
> Makes sense. I'll work on this. I didn't see a specific set of
> instructions in admin or CONTRIBUTE for how to obsolete an elisp file,
> so I'll try to follow the procedures that were used for some other
> recently-obsoleted files.
Thanks. Basically just: move the file to the lisp/obsolete directory,
add an "Obsolete-since" header, mention this in NEWS, and remove it from
the manual.
> I also noticed eudcb-bob.el; I'm not sure what it does or if anyone uses
> it. Any thoughts on that one?
I've never used it. Maybe ask
https://lists.sourceforge.net/lists/listinfo/bbdb-info ?
(I guess it may have ossified and not work with bbdb 3.)
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#21191: Obsolete eudcb-ph.el
2015-08-12 6:02 ` Glenn Morris
@ 2015-12-07 3:04 ` Thomas Fitzsimmons
2015-12-07 16:48 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Fitzsimmons @ 2015-12-07 3:04 UTC (permalink / raw)
To: Glenn Morris; +Cc: 21191, 21191-done
fixed 21191 25.1
thanks
Glenn Morris <rgm@gnu.org> writes:
> Thomas Fitzsimmons wrote:
>
>> Makes sense. I'll work on this. I didn't see a specific set of
>> instructions in admin or CONTRIBUTE for how to obsolete an elisp file,
>> so I'll try to follow the procedures that were used for some other
>> recently-obsoleted files.
>
> Thanks. Basically just: move the file to the lisp/obsolete directory,
> add an "Obsolete-since" header, mention this in NEWS, and remove it from
> the manual.
Done. Let me know if I missed anything.
>> I also noticed eudc-bob.el; I'm not sure what it does or if anyone uses
>> it. Any thoughts on that one?
I noticed references to this in the manual. I think it might still be
useful for LDAP results. I left it in for now, until I get a chance to
try it.
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#21191: Obsolete eudcb-ph.el
2015-12-07 3:04 ` Thomas Fitzsimmons
@ 2015-12-07 16:48 ` Glenn Morris
2015-12-08 0:03 ` Thomas Fitzsimmons
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2015-12-07 16:48 UTC (permalink / raw)
To: Thomas Fitzsimmons; +Cc: 21191
Thanks. One comment:
>> add an "Obsolete-since" header
Please do add an "Obsolete-since: 25.1" header to the file you moved to
obsolete/.
Some bug tracker usage comments:
No need to mail both 21191 and 21191-done.
The "fixed 21191" stuff had no effect, since you did not (b)cc the
control server.
There's various ways to close things, but the one I would have used is
to mail just "21191-done", with "Version: 25.1" on the first line of the
body.
Anyway, thanks for taking care of this issue.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#21191: Obsolete eudcb-ph.el
2015-12-07 16:48 ` Glenn Morris
@ 2015-12-08 0:03 ` Thomas Fitzsimmons
0 siblings, 0 replies; 6+ messages in thread
From: Thomas Fitzsimmons @ 2015-12-08 0:03 UTC (permalink / raw)
To: Glenn Morris; +Cc: 21191
fixed 21191 25.1
thanks
Glenn Morris <rgm@gnu.org> writes:
> Thanks. One comment:
>
>>> add an "Obsolete-since" header
>
> Please do add an "Obsolete-since: 25.1" header to the file you moved to
> obsolete/.
Oops, I dropped this by accident during a local rebase. I just pushed
the patch.
> Some bug tracker usage comments:
>
> No need to mail both 21191 and 21191-done.
>
> The "fixed 21191" stuff had no effect, since you did not (b)cc the
> control server.
>
> There's various ways to close things, but the one I would have used is
> to mail just "21191-done", with "Version: 25.1" on the first line of
> the body.
OK, thanks, trying again to mark it fixed for 25.1.
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-12-08 0:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-05 6:53 bug#21191: Obsolete eudcb-ph.el Glenn Morris
2015-08-06 6:38 ` Thomas Fitzsimmons
2015-08-12 6:02 ` Glenn Morris
2015-12-07 3:04 ` Thomas Fitzsimmons
2015-12-07 16:48 ` Glenn Morris
2015-12-08 0:03 ` Thomas Fitzsimmons
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).