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 created my git repository for me in that
> process. I don't know how or why that happened but it was a satellite
> connection yesterday and not my usual cable connection.
Oy, vey: that is pretty weird.
Just delete the whole cloned repository and clone again. I just did that
and git describe says:
,----
| $ git describe
| release_7.8.02-53-g88ef5fe
`----
Nick
On Thu, 29 Dec
> 2011, Nick Dokos wrote:
>
> > 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 Makefile to clear this problem and if so how? If
> > > not, how do I get this version to the update capability?
> > >
> >
> > You need to clone the git repository:
> >
> > git clone git://orgmode.org/org-mode.git
> > /path/to/your/local/org/mode/git/repository
> >
> > before you can use the update target in the Makefile, which just does a git
> > pull
> > before remaking:
> >
> > ,----
> > | ...
> > | update:
> > | git pull
> > | ${MAKE} clean
> > | ${MAKE} all
> > | ...
> > `----
> >
> > Note that the /path/to/your/local/org/mode/git/repository must not exist
> > beforehand:
> > it is created by the cloning process. And, of course, you need to have git
> > installed.
> >
> > Nick
> >
> >
>
> ----------------------------------------------------------------
> Jude <jdashiel-at-shellworld-dot-net>
> <http://www.shellworld.net/~jdashiel/nj.html>
>
