On Tue, Mar 25, 2014 at 2:54 PM, Bernd Paysan <[email protected]> wrote: > Am Dienstag, 25. März 2014, 14:49:46 schrieb Donald Winiecki: >> On Tue, Mar 25, 2014 at 12:58 PM, Bernd Paysan <[email protected]> wrote: >> > Am Dienstag, 25. März 2014, 12:53:53 schrieb Donald Winiecki: >> >> Fresh git of gforth doesn't build for me without earlier gforth. >> > >> > Sure, but you actually get a Gforth which you can use to build when you >> > install the Debian package? It just displays the annoying error message >> > on >> > install, which seems to stick in the package manager (which is annoying, >> > but should go away once you have installed the gforth.el from fresh git). >> Yes. It took a little looking around to figure out what to call things >> to checkout (for example: v0-7-2), but I've got your latest changes in >> gforth-0.7.2 now. No errors about gforth.elc popped up in the >> config-make-etc. process > > Which repo did you use? The one on Savanna and github should have v0-7-3 as > last tag in the v0-7 branch (the v0-7-4 tag will be added when I release > 0.7.4). > >> I didn't find a more recent version (such as, v0-7-3, etc.) so I'm >> confident I have your latest. > > I'm confident you don't have my latest.
Okay. Here's what I've done. I'm not sure what I'm missing. ...$ git clone git://git.sv.gnu.org/gforth.git ... *** then from within the freshly gotten git directory ...$ git checkout v0-7-3 ...$ error: pathspec 'v0-7-3' did not match any file(s) known to git. ...*** So I'll be more methodical this time: ...$ git checkout v0-7 Previous HEAD position was faa7759... Changelog update Branch v0-7 set up to track remote branch v0-7 from origin. Switched to a new branch 'v0-7' ...$ git checkout v0-7-3 ...$ error: pathspec 'v0-7-3' did not match any file(s) known to git. ...$ git tag alpha gforth-0_1beta git-start v0-2-0 v0-2-1 v0-3-0 v0-4-0 v0-5-0 v0-6-0 v0-6-1 v0-6-2 v0-7-0 v0-7-1 v0-7-2 ...$
