The Axiom source downloads from
http://axiom-developer.org/axiom-website/downloads/axiom-jan2009-src.tgz
contain not only the sources but a complete git tree. Thus, you can keep up
to date with the silver development (experimental, pre-release) by doing
the following:
(get the sources and git
I went ahead and started looking at the GIT tutorials. First, my
original assertion was incorrect - if handled correctly, FAQ DID change
based on which branch was active.
Based on this tutorial
(http://www.kernel.org/pub/software/scm/git/docs/tutorial.html), here
is what worked for me:
git branc
the password for the git repository is 'linus'.
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Quoting [EMAIL PROTECTED]:
Are you sure you can't commit.
I see a commit to the daly branch
Yes, the commit to the daly branch was a test to make sure that
I had the correct permissions. It used the svn client directly.
The git-svn connection does everything except commit. I'm still
puzzled a
>Are you sure you can't commit.
>I see a commit to the daly branch
Yes, the commit to the daly branch was a test to make sure that
I had the correct permissions. It used the svn client directly.
The git-svn connection does everything except commit. I'm still
puzzled about it.
Tim
> Well checkout works and I can make changes.
> I just cannot commit changes. I get
>
> Authorization failed:
> MKACTIVITY of '/svnroot/axiom/!svn/act/.:
> authorization failed (https://axiom.svn.sourceforget.net) at
> /usr/bin/git-svn line 875
>
> I'm open to suggestion about why I cannot c
Well checkout works and I can make changes.
I just cannot commit changes. I get
Authorization failed:
MKACTIVITY of '/svnroot/axiom/!svn/act/.:
authorization failed (https://axiom.svn.sourceforget.net) at
/usr/bin/git-svn line 875
I'm open to suggestion about why I cannot commit to SVN.
t
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Friday, October 27, 2006 6:11 PM Gaby wrote:
| > ...
| > I would like to see changes Tim makes to axiom--silver--1 sent to
| > this list or to the axiom-commits list. That helps keeping track
| > of the changes.
| >
|
| With the Tailor in place, I
On Friday, October 27, 2006 6:11 PM Gaby wrote:
> ...
> I would like to see changes Tim makes to axiom--silver--1 sent to
> this list or to the axiom-commits list. That helps keeping track
> of the changes.
>
With the Tailor in place, I think this will automatically happen.
Tailor creates the
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Friday, October 27, 2006 3:06 PM Waldek Hebisch wrote:
| > ...
| > Bill Page wrote:
| > > If you are able to identify and annonate the chunks of this
| > > changeset that represent deletions, additions and those that
| > > need further discussion, I t
On Friday, October 27, 2006 3:06 PM Waldek Hebisch wrote:
> ...
> Bill Page wrote:
> > If you are able to identify and annonate the chunks of this
> > changeset that represent deletions, additions and those that
> > need further discussion, I think that would be great. Except
> > for the issue of
> > I have fetsche /silver from SourceForge. I do not understand why
> > you write about big differences. The biggest difference is that
> > /silver contains .arch-ids subdirectories. AFAICS essential differences
> > are tiny (869 lines). /silver has tla-1.1.tar.gz (IIRC removed
> > from /trunk)
Bill Page wrote:
> On Friday, October 27, 2006 9:08 AM Waldek Hebisch wrote:
> > Also, /trunk has added ChangeLog to some subdirectories.
> >
>
> Maybe we need to discuss this ChangeLog policy. At one
> point Gaby started adding per directory ChangeLogs, but
> Tim has only every used one central
> I have fetsche /silver from SourceForge. I do not understand why
> you write about big differences. The biggest difference is that
> /silver contains .arch-ids subdirectories. AFAICS essential differences
> are tiny (869 lines). /silver has tla-1.1.tar.gz (IIRC removed
> from /trunk) and /trunk
On Friday, October 27, 2006 9:08 AM Waldek Hebisch wrote:
> ...
> Bill Page wrote:
> > The reason I decided to leave /trunk was that in fact there
> > are quite a large number of changes from /trunk to your new
> > /silver and resolving these differences will take some time.
> > If I just applied
> Tim,
>
> On Wednesday, October 25, 2006 9:03 PM you wrote:
> >
> > I did a checkout of the sourceforge SVN root.
> > I'll diff the SVN vs axiom--silver--1 so nothing gets lost.
> >
>
> Ok. After a little messing things up, I think I now have a
> working automatic procedure to update the SVN s
Tim,
On Wednesday, October 25, 2006 9:03 PM you wrote:
>
> I did a checkout of the sourceforge SVN root.
> I'll diff the SVN vs axiom--silver--1 so nothing gets lost.
>
Ok. After a little messing things up, I think I now have a
working automatic procedure to update the SVN silver repository
wit
Bill,
I did a checkout of the sourceforge SVN root.
I'll diff the SVN vs axiom--silver--1 so nothing gets lost.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Onednesday, October 25, 2006 6:21 PM Waldek Hebisch wrote:
>
> Bill Page wrote:
> > Well, the procedure that we agreed on (I think) was the Tim
> > would be solely responsible for committing changes to Silver
> > (axiom--silver-1 == SVN /trunk). Tim's preferred way to do this
> > is entirely a man
Bill Page wrote:
> Well, the procedure that we agreed on (I think) was the Tim
> would be solely responsible for committing changes to Silver
> (axiom--silver-1 == SVN /trunk). Tim's preferred way to do this
> is entirely a manual process - send him patches and copy the
> axiom-developer list. Pers
On Wednesday, October 25, 2006 5:08 PM Waldek Hebisch wrote:
Bill Page wrote:
> > ... Is deleteing and re-creating /trunk a safe and sensible
> > thing to do?
>
> I am not sure if it is safe, but I wonder if it has any
> advantages (like preserving history) compared to other options.
>
My plan w
First, I think we can agree that axiom--silver--1 is the master copy.
(I haven't yet looked at it but it probably contains all the history
since Tim started.)
So in fact the history in the sourceforge or google mirror of silver are
not too important.
But anyway, if they the log data should b
> One way to do this would be to first of all delete /trunk
> from the repository and rebuild it from the current contents
> of axiom--silver--1, but given the little I understand about
> how SVN works, I am concerned that using svnadmin to delete
> /trunk might have serious consequences for any br
On Wednesday, October 25, 2006 4:46 PM Ralf Hemmecke wrote:
>
> Doing a delete via svnadmin... I don't think that's the right way.
>
I am also worried about this.
> ...
> One problem with 'svn delete' applied to the trunk and then
> recreation from new files is that you basically double the s
| One way to do this would be to first of all delete /trunk
| from the repository and rebuild it from the current contents
| of axiom--silver--1, but given the little I understand about
| how SVN works, I am concerned that using svnadmin to delete
| /trunk might have serious consequences for any b
Bill,
fire up emacs, start a shell, do a
diff -r --brief axiom--silver--1 sourceforge | grep -v svn | grep -v arch
and you can see which files need to be copied.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/
"Page, Bill" <[EMAIL PROTECTED]> writes:
| Gaby,
|
| Since Tim has agreed to what I proposed below and no one
| else has disagreed, I would like to plan for this but I
| would appreciate your opinion first on how best to do it
| without screwing up the SVN repository to badly. Specfically
| what
Alfredo,
You are right. I guess I will have to talk to him anyway since
if we do this on SourceForge, we would still have the problem of
updating Google the same say. I am quite sure that my current
method of updating Google would not work properly if I were to
try to delete SourceForge /trunk and
Gaby,
Since Tim has agreed to what I proposed below and no one
else has disagreed, I would like to plan for this but I
would appreciate your opinion first on how best to do it
without screwing up the SVN repository to badly. Specfically
what we would be trying to do is to replace the existing
/tru
root <[EMAIL PROTECTED]> writes:
[...]
| SVN won't work for me so i have stopped trying to use it.
| it should "just work" and it doesn't. Gaby likes it and it works
| well for him so he uses it. Bill wrestled heroically with it.
You did not look hard enough to see for whom else it is working.
> >
> > > tla get axiom--silver--1
> > ...
> > I hope it is not too hard for you to convince "tailor" to move
> > the patches from Tim to SourceForge.
> > ...
>
> If everyone agrees (and especially, Tim Daly agrees) then I would
> delete the current SourceForge SVN /trunk and replace it with a
> > i've been unable to use SVN and could generate no interest in GIT.
>
> It's interesting to me, but I'm somewhat dismayed by the multitude of
> systems we are going through. I would have been happy to standardize
> on and learn Arch, but as it is no longer maintained that's not really
> a viab
If everyone agrees (and especially, Tim Daly agrees) then I would
delete the current SourceForge SVN /trunk and replace it with a
copy of axiom--silver--1 that is automatically maintained in sync
by running Tailor every night, like we currently do between
SourceForge and Google and between the bui
On October 25, 2006 5:18 AM Ralf Hemmecke wrote:
>
> > tla get axiom--silver--1
> ...
> I hope it is not too hard for you to convince "tailor" to move
> the patches from Tim to SourceForge.
> ...
If everyone agrees (and especially, Tim Daly agrees) then I would
delete the current SourceForge SV
> You see, Tim applied patches to his Gold-to-be and now Silver is no
longer in sync with that. Tim, mirror your Gold-to-be branch publicly
and accept the offer of Bill to move your changes to sourceforge.
How to move things from any other place back to Tim is another issue.
But the mailing-list
--- root <[EMAIL PROTECTED]> wrote:
> i've been unable to use SVN and could generate no interest in GIT.
It's interesting to me, but I'm somewhat dismayed by the multitude of
systems we are going through. I would have been happy to standardize
on and learn Arch, but as it is no longer maintained
> I fetched silver from SourceForge. The last ChangeLog entry is from
> 2006-09-14 (so it is somewhat old) and it has build problems (fixed
> in build-improvenents): one has to remove by hand '.svn' subdirectories,
> full Latex installation is needed. I fetched silver about two
> weeks ago, but
currently gold exists in arch (axiom--main--1) and in the CVS
on sourceforge and savannah. i had planned to keep the silver
branch up to date at the root of SVN but SVN fails to work for me.
i've been unable to use SVN and could generate no interest in GIT.
i've created a silver branch in the arc
"Bill Page" <[EMAIL PROTECTED]> writes:
[...]
| So far as I know, no one has been updating SourceForge SVN /trunk
| aka. "silver" lately. It was originally created by converting the
| CVS version of patch-49 at SourceForge to SVN using the SourceForge
| CVS to SVN migration tool. Gaby branched bu
On October 24, 2006 9:26 PM Waldek Hebisch wrote:
>
> Bill Page wrote:
> > On October 24, 2006 2:53 PM Jay Belanger wrote:
> > > I could check out from google, but it was an older version that
> > > had build problems.
> >
> > ???
> >
> > To the best of my ability to make this true, the contents
Bill Page wrote:
> On October 24, 2006 2:53 PM Jay Belanger wrote:
> > I could check out from google, but it was an older version that
> > had build problems.
>
> ???
>
> To the best of my ability to make this true, the contents of
> the SVN repository on Google is identical the the SourceForge
>
On October 24, 2006 2:53 PM Jay Belanger wrote:
>
> "Bill Page" <[EMAIL PROTECTED]> writes:
> ...
> >> but svn had stopped working for me, and git finally gave me
> >> a working silver branch of Axiom, and quickly, too.
> >>
> >
> > What was your problem svn? Did you try the Google Code mirror?
>
"Bill Page" <[EMAIL PROTECTED]> writes:
...
>> but svn had stopped working for me, and git finally gave me a
>> working silver branch of Axiom, and quickly, too.
>>
>
> What was your problem svn? Did you try the Google Code mirror?
When I tried to check out from axiom-developer, I kept getting er
Jay,
On October 24, 2006 10:49 AM you wrote:
>
> I hope I'm not just cluttering up the mail list with more talk
> about revision control systems,
You can't clutter up something that is already cluttered up... ;)
> but svn had stopped working for me, and git finally gave me a
> working silver br
I hope I'm not just cluttering up the mail list with more talk about
revision control systems, but svn had stopped working for me, and git
finally gave me a working silver branch of Axiom, and quickly, too.
"Bill Page" <[EMAIL PROTECTED]> writes:
...
> But Mercurial is faster (and some say better
> On October 23, 2006 7:11 PM Jay Belanger
> >
> > root <[EMAIL PROTECTED]> writes:
> >
> > > man, this git thing is blindingly fast.
> >
> > It certainly is. I just got a copy of silver Axiom using git.
> > It seems as if git got the whole thing in less time than it took
> > svn to get a few
On October 23, 2006 7:11 PM Jay Belanger
>
> root <[EMAIL PROTECTED]> writes:
>
> > man, this git thing is blindingly fast.
>
> It certainly is. I just got a copy of silver Axiom using git.
> It seems as if git got the whole thing in less time than it took
> svn to get a few files from the zip
root <[EMAIL PROTECTED]> writes:
> man, this git thing is blindingly fast.
It certainly is. I just got a copy of silver Axiom using git. It
seems as if git got the whole thing in less time than it took svn to get a
few files from the zip directory.
Jay
__
man, this git thing is blindingly fast.
as it says in the docs sometimes you don't think anything happened.
i put up a git version of all of the current changes since --patch-50
you can get an axiom copy with:
git clone [EMAIL PROTECTED]:/home/silver/silver
password: (send email to [EMAIL
Has anyone used Git in any project?
I found this page:
http://keithp.com/blog/Repository_Formats_Matter.html
where he states that:
The Mozilla CVS repository was 2.7GB, imported to Subversion it
grew to 8.2GB. Under Git, it shrunk to 450MB. Given that a Mozilla
checkout is around 350MB, it's fai
50 matches
Mail list logo
