Menu
▾
▴
Re: [Cscope-devel] xcscope.el maintainership
|
From: Darryl O. <da...@so...> - 2013-07-31 23:03:23
|
I'm still here, although I've had no time for anything. If the patches are still in the tracker, point me to them, and I'll take a look and try to merge them. I'll have to again learn how to use sourceforge, though. I think I still have commit permission for the .el files. This may have to wait until the weekend, however. -- Darryl > Dima Kogan <mailto:cs...@di...> > Wednesday, July 31, 2013 3:57 PM > > OK. Let me contact Darryl before moving forward on this thread. > > Thanks > > dima > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Cscope-devel mailing list > Csc...@li... > https://lists.sourceforge.net/lists/listinfo/cscope-devel > > Hans-Bernhard Bröker <mailto:HBB...@t-...> > Tuesday, July 30, 2013 1:57 PM > On 30.07.2013 21:04, Dima Kogan wrote: > >> What do you suggest I ask him? Whether he'll soon review the >> patches/bugs in the tracker assigned to him? It's been years, so I think >> we know the answer to that. > > There's always the possibility that he just forgot about cscope, and > needs a reminder. The only way to actually find out the answer is to > ask the question. > >> That's definitely a possibility. I'd personally prefer not to deal with >> sourceforge/cvs, but this is fine if we can agree that the current place >> for that code is the right one. My reasoning for splitting out this code >> is that there are many other interfaces to cscope, and most of them are >> NOT in the repo. > > There be many interfaces, but most of those are stand-alone shells on > top of cscope. xcscope.el and the VIM cscope package are unique in that > they sit _between_ two programs, which makes them depend on both of > them. Distributing such two-way interfaces with either the editor or > cscope makes a good deal more sense than it would for, say, kscope or > other GUIs. > >> This one is in the repo; is this because at one point >> Darryl was actively maintaining it here? > > That's exactly the reason. > >> As it stands right now, the >> presense of xcscope.el in the main repo implies that this interface is >> somehow more actively supported than the others, and this simply isn't >> true. > > Which is why we owe it to Darryl Okahata to at least ask him before we > change this, either way. > >> I could join the project as "the xcscope.el guy". Would that be >> preferable to splitting it out? Or should I just go through the tracker >> and send you patches? > > If you're going to be acting on this on any kind of regular basis, you > should join up. I cannot meaningfully review patches to elisp anyway, > so there would be no point in passing them by me. > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Cscope-devel mailing list > Csc...@li... > https://lists.sourceforge.net/lists/listinfo/cscope-devel > Dima Kogan <mailto:cs...@di...> > Tuesday, July 30, 2013 12:04 PM > Hans-Bernhard Bröker<HBB...@t-...> writes: > >> On 28.07.2013 09:02, Dima Kogan wrote: >> >>> These are all assigned to Darryl, who I assume is no longer active. >> Well, you could always ask Darryl directly. Haven't heard from him in a >> long time, but he might still be reachable. > > What do you suggest I ask him? Whether he'll soon review the > patches/bugs in the tracker assigned to him? It's been years, so I think > we know the answer to that. > > >>> and I'd like to ask: does it make sense for these bindings to continue >>> being distributed here? How would yall feel about splitting out that >>> part of the repository into a separate project, and I can then take on >>> maintainership of that code. I am a regular user of those bindings, so >>> this should be a working arrangement. >> Or you could do that inside the cscope project. Our release cycle has >> been very slow these last few year, but it should be possible to >> organize a release of cscope once you have done all those xcscope >> patches you consider necessary. > > That's definitely a possibility. I'd personally prefer not to deal with > sourceforge/cvs, but this is fine if we can agree that the current place > for that code is the right one. My reasoning for splitting out this code > is that there are many other interfaces to cscope, and most of them are > NOT in the repo. This one is in the repo; is this because at one point > Darryl was actively maintaining it here? As it stands right now, the > presense of xcscope.el in the main repo implies that this interface is > somehow more actively supported than the others, and this simply isn't > true. > > I could join the project as "the xcscope.el guy". Would that be > preferable to splitting it out? Or should I just go through the tracker > and send you patches? > > Thanks > > dima > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Cscope-devel mailing list > Csc...@li... > https://lists.sourceforge.net/lists/listinfo/cscope-devel > Hans-Bernhard Bröker <mailto:HBB...@t-...> > Sunday, July 28, 2013 4:09 AM > On 28.07.2013 09:02, Dima Kogan wrote: > >> These are all assigned to Darryl, who I assume is no longer active. > > Well, you could always ask Darryl directly. Haven't heard from him in a > long time, but he might still be reachable. > >> and I'd like to ask: does it make sense for these bindings to continue >> being distributed here? How would yall feel about splitting out that >> part of the repository into a separate project, and I can then take on >> maintainership of that code. I am a regular user of those bindings, so >> this should be a working arrangement. > > Or you could do that inside the cscope project. Our release cycle has > been very slow these last few year, but it should be possible to > organize a release of cscope once you have done all those xcscope > patches you consider necessary. > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Cscope-devel mailing list > Csc...@li... > https://lists.sourceforge.net/lists/listinfo/cscope-devel > Dima Kogan <mailto:cs...@di...> > Sunday, July 28, 2013 12:02 AM > Hi. > > I noticed that the cscope emacs bindings (xcscope.el) appear to be > relatively unmaintained. The last commit was a patch I submitted earlier > this year: > > https://sourceforge.net/p/cscope/patches/79/[1] > > The last commit before that happened in 2002. In the meantime there are > plenty of patches and bugs in the tracker that have been open for years. > These are all assigned to Darryl, who I assume is no longer active. > > I just fixed another bug, and submitted a patch: > > https://sourceforge.net/p/cscope/bugs/285/[2] > > and I'd like to ask: does it make sense for these bindings to continue > being distributed here? How would yall feel about splitting out that > part of the repository into a separate project, and I can then take on > maintainership of that code. I am a regular user of those bindings, so > this should be a working arrangement. > > Thanks > > dima > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Cscope-devel mailing list > Csc...@li... > https://lists.sourceforge.net/lists/listinfo/cscope-devel |