On October 24, 2006 1:53 PM Ralf Hemmecke wrote: > > Nevertheless, last week you thought about making your Gold-to-be > public. We should have your tla branch and Silver on sourceforge > and google in sync. Everything else confuses people no matter how > many SCM-systems we use for axiom. >
I think that if Tim likes git, then dropping arch (tla) in favour of git would be big step forward - not as nice as if everyone could agree on some just one SVM, but much better. At least Tailor would allow simple two-way sync'ing between git and svn (and hg and darcs) where as this is not possible with tla. I use Tailor now to keep darcs and hg versions of build-improvements branch in sync with Gaby's svn branch every night. Adding git to this automatic interchange would be very simple. I can add a paragraph in the Experiment section of AxiomSources for git if you like. Regards, Bill Page. > > On 10/24/2006 05:20 PM, root wrote: > >>>> I guess that intention here was to avoid hangs, but this does not > >>>> work! To make '--interaction nonstopmode' effective one has to > >>>> give it _before_ file name. So the form below is immune to hangs: > >>> ah, that's useful to know. > >>> > >>> fixed in the next release. > >>> > >>> t > >> Cool! Were you recently saying that your Gold-To-Be is now > >> available as a git archive? I fear sourceforge Silver is already > >> out-of-date. > >> > >> Hmmm... yet another version control system and seemingly > no documentation at > >> > >> http://wiki.axiom-developer.org/AxiomSources > >> > >> so the git stuff is burried in the mail archive. :-( > > > > you've read about my many efforts to try to use the sourceforge SVN > > and the frustrations and failures. > > > > a lot of the reading i did also mentioned 'git', apparently written > > by Linus after BitKeeper was pulled. so i read up on it and decided > > to try it. i set up a silver userid on axiom-developer, > copied in the > > gold branch, applied the latest patches locally. then i tried to > > clone the branch on a remote machine, then remotely modify > the branch > > and push it back to axiom-developer. total effort was about 1 hour. > > no server process is required. no setup. no Perl. > > > > works like magic. doesn't fail. doesn't mangle binaries. blindingly > > fast. easy to use. in fact, it is so fast that making source patches > > feels like doing a local copy. the side-effect is that it feels easy > > to maintain source code. > > > > once cloned, push and pull just work. so keeping remote copies > > in sync is trivial, unlike the pain Bill experienced trying to > > get Google syncing to work. > > > > anyway, at this point it is just an experiment. > > i just applied the --interaction patch to see if Jay can pull it. > > > > t > > > _______________________________________________ > Axiom-developer mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/axiom-developer > > _______________________________________________ Axiom-developer mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/axiom-developer
