RFU jed 1:0.99.19~pre143-1

Jörg Sommer joerg at alea.gnuu.de
Sat Jun 28 09:54:23 UTC 2008


Hallo Rafael,

Rafael Laboissiere schrieb am Fri 27. Jun, 09:52 (+0200):
> * 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

Your working tree is not clean. The same should tell you git status. Run
debian/rules clean or git reset --hard; git clean -d

> 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.

But that's the same as with svn. If you have uncommited files in your
working tree in svn you get also warned when you run svn up.

Bye, Jörg.
-- 
at lilo press tab key | an Luftmatratzenpressetabulatorschlüssel
(Übersetzung von Personal Translator 2000)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature http://en.wikipedia.org/wiki/OpenPGP
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20080628/1bb7b00c/attachment.pgp 


More information about the Pkg-jed-devel mailing list