From: Robert G. <rpg...@si...> - 2009-01-25 17:29:48
|
Gary King wrote: > As discussed previously, I'd like to move asdf from sourceforge to > cl.net. I'd also like to move from CVS to git. I also want to make > things as simple as possible for all the stakeholders (i.e., the lisp > community, the cCLan creators and maintainers, me (!)). > > I'm not a VCS-maven and haven't found any brain-dead simple cvs to git > converters that are come with only praise. The easiest thing (for me) > to do would be to checkout the head of the ASDF repository and start a > fresh git image from there. > > # Pros > > * it's easy > * requires no research into software tools > * it could be done today! > > # Cons > > * we lose easy access to the history of the repository > > I personally don't mind losing the history but if there are those that > do, speak up! Also, if there are those that have experience > transitioning from CVS to git and can tell me how to do it easily, let > me know! > > If I don't hear any protests, I'll move ASDF into git without its > history by Tuesday. Protest! ;-) I like the move from ASDF into git, all things considered. For one thing my import of Marco's clean-op is pretty much derailed by my inability to create a branch.... Two points: 1. I really would prefer that we not lose the history. I can't imagine that this is really that hard. My company has had great success dumping cvs with full history into SVN, so I can't believe that passing from cvs to git is impossible. I *have* heard that the cvs->git tools are not bulletproof and read at least one web article claiming that cvs->svn->git is a better path; that the two links in that path are better than the single link in the direct one. I have no way of evaluating this hearsay. 2. Please explain to us the working pattern for ASDF + git. E.g., I occasionally submit a small patch or two to Carsten Dominik's org-mode, and I am happy that he has clearly explained the git-usage pattern. For that project, you pull from Carsten, branch, develop new code, create a patch, submit to Carsten and, if all goes well, it goes into Carsten's master repo. Is this a workable pattern for ASDF? If not, do you have something different in mind? git is such a flexible tool that (at least to me) saying we're going to move to git doesn't tell me how we're going to work as a community. Thanks, R |