> > > I'm really bad coordinator. > > > I'd like to improve my wrong procedures to handle the copyright > > > issue. > > > > Well, it hasn't been a really big problem up to now, since the merge > > into GNU Emacs did not happen. > > > > For those who didn't see the news, Emacs 22 is out, so I believe this > > is time to really think about an inclusion into Emacs 23. Even though > > DVC is not really "finished", it's probably worth asking the Emacs > > guys what they think about it. > > > > Thoughts? > > The paper work for FSF is being done background by Michael Olson and I. > I'll report progress when we get progresses.
I'm very sorry to be late. Could you someone take over the task? I'd like to step back from the task. Some reasons: 1. I have some troubles in my private life, 2. I get more interests to extend vc-dired, and 3. I could not find the first step to merge DVC to Emacs. I feel DVC is too large for me. I could not understand what functions are implemented in backends. Even if it is implemented, I'm not sure the quality of implementation. Maybe because I'm away too long from DVC development. I think some of functions of DVC should be implemented in vc or vc-dired. There are some duplicated code and function among DVC and VC. e.g. annotation. Maybe DVC's annotation implementation is better because DVC does most of things asynchronously. My merge plan was that: A. moving DVC code to VC, then B. reorganizing the rest, then C. merging the rest to Emacs. However, I found I cannot take much time till this September. Further more you, who don't use dired, may not agree with this merge plan. I'd like to concentrate on A. privately. Forgive me this selfish approach and behavior. However, on emacs-devel list people are talking about (distributed) versoin control systems used in GNU Emacs development now. So I think I should notify my position and thought DVC now. Masatake YAMATO _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
