>The cvs tree doesn't have any .cvsignore files, neither 5.0 or 5.1
>branch. It's correct?
I'm afraid I don't know what a .cvsignore file does. Please explain?
>When you use the same CVS tree downloaded to compile, you have to inform
>what files is automatic generated by your source on compile time and
>have to be ignored by CVS update. This files will not be syncronized
>with CVS.
>
>This is an .cvsignore example for src/bin32/.cvsignore
>*.o
>*.rom
>*.lzrom
>*.tmp
>*.huf
Ok. I guess I never used one because I always do a make clean before
doing a commit.
From: Gustavo J. A. <al...@co...> - 2001-12-27 13:19:10
Will be nice! :-)
Ken Yap wrote:
>>Those are the patches for .cvsignore.
>>
>
>Ok, thanks, will add. Would you like to be a registered developer?
>
>_______________________________________________
>Etherboot-developers mailing list
>Eth...@li...
>https://lists.sourceforge.net/lists/listinfo/etherboot-developers
>
>Will be nice! :-)
>
>Ken Yap wrote:
>
>>>Those are the patches for .cvsignore.
>>
>>Ok, thanks, will add. Would you like to be a registered developer?
Ok, register yourself at sourceforge.net and then mail me your Unix
login ID.
From: Gustavo J. A. <al...@co...> - 2001-12-19 17:22:34
When you use the same CVS tree downloaded to compile, you have to inform
what files is automatic generated by your source on compile time and
have to be ignored by CVS update. This files will not be syncronized
with CVS.
This is an .cvsignore example for src/bin32/.cvsignore
*.o
*.rom
*.lzrom
*.tmp
*.huf
Gustavo Junior Alves
al...@co...
Ken Yap wrote:
>>The cvs tree doesn't have any .cvsignore files, neither 5.0 or 5.1
>>branch. It's correct?
>>
>
>I'm afraid I don't know what a .cvsignore file does. Please explain?
>
>_______________________________________________
>Etherboot-developers mailing list
>Eth...@li...
>https://lists.sourceforge.net/lists/listinfo/etherboot-developers
>