Then perhaps something more is wrong. I downloaded orgmode-7.8.02 and
installed that after having run the standard gitclone command to clone
org-mode on this system. I did that because the gitclone process pulled
version 5.23 for me and also created my git repository for me in that
process.
Jude DaShiell jdash...@shellworld.net wrote:
Then perhaps something more is wrong. I downloaded orgmode-7.8.02 and
installed that after having run the standard gitclone command to clone
org-mode on this system. I did that because the gitclone process pulled
version 5.23 for me and also
Jude DaShiell jdash...@shellworld.net wrote:
Once that was done I figured to run make ./update in the org-7.8.02
directory and get the latest patches. No cigar, this isn't within any git
repository apparently on my end so couldn't be pulled by make ./update.
Do I need to edit the
Once that was done I figured to run make ./update in the org-7.8.02
directory and get the latest patches. No cigar, this isn't within any git
repository apparently on my end so couldn't be pulled by make ./update.
Do I need to edit the Makefile to clear this problem and if so how? If
not,
We're now golden. When I ran git describe I was told no repository
exists. So I ran git init and created an empty repository and then ran
the git clone command and this time aI have an installed version of 7.8.02
and am told I'm up to date. Apparently running a git clone operation on
On Thu, Dec 29, 2011 at 3:12 PM, Jude DaShiell jdash...@shellworld.netwrote:
We're now golden. When I ran git describe I was told no repository
exists. So I ran git init and created an empty repository and then ran
the git clone command and this time aI have an installed version of 7.8.02
On 12/29/2011 07:02 PM, Jude DaShiell wrote:
Then perhaps something more is wrong. I downloaded orgmode-7.8.02 and
installed that after having run the standard gitclone command to clone
org-mode on this system. I did that because the gitclone process pulled
version 5.23 for me and also created