RFU jed 1:0.99.19~pre143-1

[Rafael Laboissiere]

* Rafael Laboissiere <rafael at debian.org> [2008-06-27 11:17]:

> * Rafael Laboissiere <rafael at debian.org> [2008-06-27 09:52]:
> 
> > * Jörg Sommer <joerg at alea.gnuu.de> [2008-06-26 13:58]:
> > 
> > > Now you can go on:
> > > 
> > > % git fetch
> > > % git co -b new origin/0.99.19
> > > Branch new set up to track remote branch refs/remotes/origin/0.99.19.
> > > Switched to a new branch "new"
> > 
> > I got rather this:
> > 
> > $ git co -b new origin/0.99.19
> > T       autoconf/config.guess
> > T       autoconf/config.sub
> > M       doc/README
> > M       doc/manual/jed.1
> > M       lib/acompile.sl
> > M       lib/binary.sl
> > M       lib/bookmark.sl
> > M       lib/ctags.sl
> > D       lib/emul.sl
> > M       lib/menu.sl
> > M       lib/mouse.sl
> > M       lib/replace.sl
> > M       lib/site.sl
> > M       src/Makefile.in
> > M       src/jed-feat.h
> > M       src/xterm.c
> > Branch new set up to track remote branch refs/remotes/origin/0.99.19.
> > Switched to a new branch "new"
> > 
> > Is it normal?  Sorry, I am really confused with git.
> 
> Ok, I got around the problem by starting anew with git clone.

Oh, "./debian/rules clean" would be enough.  I completely forgot that the
upstream files are being maintained in our git repository.

-- 
Rafael