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 Cscope-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cscope-devel
