Re: 1.4 on git

2012-05-07 Thread Andre Terra
add "django==1.4" to a requirements.txt file (no quotes!) $ pip install -R requirements.txt On Mon, May 7, 2012 at 1:00 AM, Rivsen wrote: > Hi Larry, > > I cloned django and django-old from github, and I found the git index of > yours. > > It's in django-old repo, not in django. > > So you nee

Re: 1.4 on git

2012-05-06 Thread Rivsen
Hi Larry, I cloned django and django-old from github, and I found the git index of yours. It's in django-old repo, not in django. So you need clone django-old not django. git clone git://github.com/django/django-old.git cd django-old git checkout -b test -f *6fbf282ac2* * * git log commit *6

Re: 1.4 on git

2012-05-06 Thread Larry Martell
On Sun, May 6, 2012 at 12:54 PM, Ramiro Morales wrote: > You will need to read the Git documentation because we are in Git territory > now. > > )ou got the latest development code by default but remember that when > you clone you get (most of) the development history and it is > available locally

Re: 1.4 on git

2012-05-06 Thread Ramiro Morales
You will need to read the Git documentation because we are in Git territory now. )ou got the latest development code by default but remember that when you clone you get (most of) the development history and it is available locally. You need to get a checkout of the commit pointed to by the '1.4'

Re: 1.4 on git

2012-05-06 Thread Larry Martell
On Sat, May 5, 2012 at 7:06 PM, Ramiro Morales wrote: > On Sat, May 5, 2012 at 8:42 PM, Larry Martell wrote: >> Last month I set up a system and when I cloned django from git I got >> version 1.4. Now I an setting up another system, and when I clone >> django from git I get 1.5, and my app is fai

Re: 1.4 on git

2012-05-06 Thread Larry Martell
On Sat, May 5, 2012 at 9:30 PM, Rivsen wrote: > Simply, you can see what git index in your first system, run "git log" and > remember the first row of commit( need only remember the first six or eight > like this 'commit 42198ad13560c46070223e095f787dff5bd8a918'  ). > > Then checkout this commit i

Re: 1.4 on git

2012-05-05 Thread Rivsen
If you want save this git index in a new branch, you can run 'git checkout -b -f *42198ad1*', then you will get a new branch with * 42198ad1* index. Best regards, Rivsen 2012/5/6 Rivsen > Simply, you can see what git index in your first system, run "git log" and > remember the first row of co

Re: 1.4 on git

2012-05-05 Thread Rivsen
Simply, you can see what git index in your first system, run "git log" and remember the first row of commit( need only remember the first six or eight like this 'commit *42198ad1*3560c46070223e095f787dff5bd8a918' ). Then checkout this commit in your second system, run 'git checkout *42198ad1 *' a

Re: 1.4 on git

2012-05-05 Thread Ramiro Morales
On Sat, May 5, 2012 at 8:42 PM, Larry Martell wrote: > Last month I set up a system and when I cloned django from git I got > version 1.4. Now I an setting up another system, and when I clone > django from git I get 1.5, and my app is failing. How I can get 1.4? I > see a django-nonrel / django-1.

1.4 on git

2012-05-05 Thread Larry Martell
Last month I set up a system and when I cloned django from git I got version 1.4. Now I an setting up another system, and when I clone django from git I get 1.5, and my app is failing. How I can get 1.4? I see a django-nonrel / django-1.4 but it says "Work in progress 1.4 port, DON'T USE" -- You