»¶Ó¹âÁÙÁªÃËÍøÕ¾£££££££££££
Title: »¶Ó¹âÁÙÁªÃËÍøÕ¾ µØÖ·(Add.)£º¶Ø»ÍÊÐÑô¹ØÎ÷·18ºÅ¡¡ÓÊÕþ±àÂ룺736200 µç»°(Tel.)£º+86-0937-8836058 0937-8823155-8266 ´«Õ棺0937-8841337¡¡E-mail£º [EMAIL PROTECTED]
ChemNet.comChemyahoo.com
Title: Chemnet.com ChemNet.com×ÔÓëµÂ¹úBuyersGuideChem.de¡¢°Ä´óÀûÑÇChemlink .com.au³É¹¦ºÏ×÷ºó£¬ÈÕÇ°ÓÖÉÏÈ«ÇòÕ½ÂÔÐĄ̂½×£¬ÓÚ2ÔÂ28ÈÕÕýʽºÏ²¢È«Çò×î´óµÄ»¯¹¤Êý¾Ý¿â¼°ËÑË÷ÒýÇæChemyahoo.com£¬Â¡ÖØÍƳö¼¯Ò»Á÷µÄÐÅÏ¢Ìṩ¡¢¶¥¼¶×¨ÒµËÑË÷ÒýÇæ¡¢ÐÂÒ»´úB2B½»Ò×ϵͳΪһÌåµÄÈ«Çò»¯¹¤ÃÅ»§¡£ ºÏ²¢ºó½«Ê¹ÓÃChemnet.comÆ·ÅÆ£¬ÔChemyahoo.comÓû§¿ÉÔÚChemnet.comÉϼÌÐøÏíÊÜÆäÔÏàÓ¦·þÎñ¡£ChemNet.com½«Ç¿Á¦Íƶ¯È«Çò»¯¹¤ÆóÒµ¿ªÍعú¼ÊóÒס£ ÊÀ ½ç »¯ ¹¤ ÃÅ »§ , ¹ú ¼Ê ÉÌ Ã³ ͨ µÀ ! È«Çò»¯¹¤Íø£¨www.chemnet.com£©ÊÇÊÀ½çÊ×Ñ¡µÄ»¯¹¤ÃÅ»§ÍøÕ¾¡£Ëü¼¯È«Çò»¯¹¤ÍøÂçÐÅÏ¢Óëµç×ÓÉÌÎñÖ®´ó³É£¬½«ÊÀ½çÒ»Á÷µÄÐÅÏ¢Ìṩ¡¢ËÑË÷ÒýÇæ¡¢½»Ò×ϵͳºÏΪһÌ壬ΪȫÇò»¯¹¤¿ÍÉÌÌṩÁË׿ԽµÄÔÚÏßÉÌóƽ̨¡£ ÍøÕ¾ÓÅÊÆ www.chemnet.comÒÔÆäÌØÊâµÄÀúÊ·Ô¨Ô´ºÍÈ«ÇòÓ°ÏìÁ¦£¬¼®ÊÀ½çÁìÏȵÄB2B½»Ò×ϵͳ¡¢×¨ÒµÒýÇæºÍÐÅÏ¢×ÊÔ´£¬ÎªÄúÌṩÎ޿ɱÈÄâµÄÉÌÒµÏÈ»ú-- 1£®www.chemnet.comÓòÃûÓÐÁùÄêÀúÊ·£¬ÖÜתÊÀ½çËÄ´óÖÞÁù¸ö¹ú¼ÒÃûÂúÈ«Çò 2£®ºÏ²¢È«Çò×î´óµÄ»¯¹¤Êý¾Ý¿â¼°ÒýÇæChemyahoo.com£¬ÍƳö¶¥¼¶×¨ÒµÄ¿Â¼ÒýÇæ 3£®Í¬ÃÀ¹ú¡¢µÂ¹ú¡¢º«¹ú¡¢ÈÕ±¾¡¢°Ä´óÀûÑǵȻ¯¹¤ÍøÕ¾½áÃËΪȫÇò»¯¹¤¹²Í¬Ìå" 4£®ÄÚÖùúÄÚÊ×´´¡¢¹ú¼ÊÁìÏÈ£¬¸Äд´«Í³½»Ò×·½Ê½µÄÐÂÒ»´úÕæÕýB2B½»Ò×ϵͳ 5£®¹úÄÚ»¯¹¤ÃÅ»§Öйú»¯¹¤ÍøÇãÁ¦Í¶È룬ºÏÁ¦´òͨ»¥¶¯È«ÇòµÄóÒ×ͨµÀ ÖªÃû¶È ¹ú¼Ê£ºChemNetÊÇÓÉÓ¢ÎÄchemical(»¯¹¤)network£¨ÍøÂ磩¼ò³Æ×éºÏ¶øÀ´£¬¹«ÈÏÓÐÖ±¹ÛµÄ»¯¹¤ÍøµÄÒâ˼,ÊÇ»¯¹¤ÍøÂç½çµÄȨÍþÓòÃû¡£ www.chemnet.comµ®ÉúÓÚ1995Äê2ÔÂ,ÏȺóÖÜתÃÀ¹ú¡¢Ó¡¶È¡¢ Èðµä¡¢°Ä´óÀûÑÇ¡¢º«¹ú¡¢ÖйúËÄ´óÖÞÁù¸ö¹ú¼Ò£¬ÃûÂúÈ«Çò¡£ÒÔ¸ÃÓòÃû¼ÓÉÏÆäËû¹ú¼Ò»òµØÇøÓòÃûºó׺µÄÑÜÉúÓòÃû¹¹½¨µÄƽ̨¾ÍÓÐ100¶à¸ö£¬Á´½Ó±é²¼È«Çò¸÷´óËÑË÷ÒýÇæºÍ»¯¹¤ÉÌÒµ¡¢¿ÆÑС¢½ÌÓýµÈ»ú¹¹£¬ÎªÈ«ÇòµÄ»¯¹¤¿ÍÉÌËùÊìÖª¡£ ¹úÄÚ£ºÖйú»¯¹¤ÍøÔÚ¿ç¹ú¹Ù˾Öл÷°Ü°Ä´óÀûÑÇ×î´óµÄ»¯¹¤¼¯ÍÅORICA¹«Ë¾£¬Ó®µÃÎÒ¹úÈëÊÀ¿ç¹ú֪ʶ²úȨ¾À·×µÚÒ»°¸£¬ Áî¼ÛֵǧÍòÃÀ½ðµÄÓòÃûwww.chemnet.comÂ仧Öйú£¬²¢ÔÚ´ËÓòÃûÏ´´½¨ÁËÊÀ½çÊ×Ñ¡µÄ»¯¹¤ÃÅ»§ÍøÕ¾£¬³ÉΪÈËÃñÈÕ±¨¡¢CCTV¡¢Ð»ªÉç¡¢Öйú¹ú¼Ê¹ã²¥µç̨¡¢ÖÐÐÂÉç¡¢ÖйúÈÕ±¨¡¢Ïã¸ÛÎĻ㱨¡¢½â·ÅÈÕ±¨¡¢Öйú»¯¹¤±¨¡¢ÑÅ»¢¡¢ÐÂÀË¡¢ËѺüµÈÖ÷Á÷ýÌå¹Ø×¢µÄ½¹µã,£¬400¶à¼ÒýÌå²ÎÓ뱨µÀ£¬¾Ù¹úÖõÄ¿¡£ Ö÷ÒªÀ¸Ä¿ 1£®»¯¹¤Ä¿Â¼(Directory) 2£®½»Ò×ÖÐÐÄ(Exchange) 3£®Êý¾Ý¿â(Suppliers) 4£®Ã³Ò×»ú»á(Trade Leads) 5£®Õ¹»áÐÅÏ¢(Expo) 6£®»¯¹¤×Öµä(Dictionary) ׿Խ·þÎñ È«Çò»¯¹¤Íø׿ԽµÄ·þÎñÆ·ÖÊÌåÏÖÔÚÆ䳬Խ³£¹æµÄ·þÎñÀíÄî--Ϊ»¯¹¤Óû§´òÔìÈ«Çò»¯µÄÐÐÒµÃÅ»§¡¢ÓªÔì¹ú¼Ê»¯µÄÉÌó»·¾³¡¢ÌṩÁìÏÈÊÀ½çµÄ½»Ò×ϵͳ¡£ 1£® ΪÆóÒµËÜÔì¹ú¼ÊÐÎÏó¡¢Ê÷Á¢¹ú¼ÊÆ·ÅÆÌṩ¿ì½Ý¡¢ÓÐЧµÄ;¾¶¡£ 2£® ƽ̨±é²¼È«ÇòµÄ·ÃÎÊÕß¼°ºÏ×÷»ï°éÓªÔìÒ»Á÷µÄ¹ú¼Ê»¯ÉÌó»·¾³ 3£® ƽ̨µÄ½»Ò×ϵͳ£¨Exchange£©ÌṩÐÂÒ»´úÍêÉƸßЧµÄµç×ÓÉÌÎñ½â¾ö·½°¸¡£ ·þÎñÏîÄ¿ È«Çò»¯¹¤Íøwww.chemnet.comÔÚÖйú´ó½ĿǰÖ÷ÒªÌṩ¾²Ì¬¹ã¸æ¡¢¹Ø¼ü×Ö¹ã¸æ¡¢Öйú¹©Ó¦É̺ÍÃâ·Ñ¶þ¼¶ÓòÃû×¢²áËÄÏî·þÎñ¡£ »¯¹¤ÃÅ»§--ÐÐÒµÐÅÏ¢¾¡À¿ÑÛµ×£¡ ÒÔÉÌΪ±¾--ÖúÄú¿ªÍØÈ«ÇòÉÌ»ú£¡ º¼ÖÝÖл¯ÍøÂçÓÐÏÞ¹«Ë¾ ¡¡Tel:0086-571-88868638¡¡ Fax:0086-571-88868972
Bug: Name keyword expansion
Hello! When updating a File (with options: retrieve tag) which is already local with the correct revision, the keyword 'Name' is not expanded. I think it is OK not to update the File, but the Keyword 'Name' should be expanded nevertheless. I think it is a bug! Best Regards Uwe Hamburger -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
bug-cvs@gnu.org
±±¾©¶«·½Óïͨ·ÒëÖÐÐÄÊÇÔÚ¹¤É̾ÖÕýʽע²áµÄÒÔÍâÎÄ·ÒëΪÖ÷µÄרҵ·þÎñ»ú¹¹£¬ÓÈÆäÉó¤¸÷רҵ¼¼ÊõÎļþ¡¢×ÊÁÏ¡¢Êé¼®µÄ·Òë¡¢ÍøÕ¾ºº»¯¼°ÍâÎÄÍøÕ¾ÖÆ×÷¡£ ÎÒÃǵķÒ붼ÊÇÓÐÊ®ÄêÒÔÉϹ¤×÷¾ÑéµÄרҵÈËÔ±£¬·ÒëÖÊÁ¿¿É¿¿¡£ ÎÒÃÇÓµÓÐÒ»Ì×ÑϸñµÄÖÊÁ¿¹ÜÀíÌåϵ£¬±¾×Å¡°ÖÊÁ¿¡¢Ð§ÂÊ¡¢°²È«¡¢·½±ã¡±µÄ·þÎñ×ÚּΪ¹ã´óÖÐÍâ¿Í»§ÌṩÓÅÖÊ¡¢Ñ¸½Ý¡¢¹æ·¶¡¢¿É¿¿µÄ·þÎñ¡£ ÓïÖÖ£ºÓ¢ÓµÂÓÈÕÓÆÏÌÑÑÀÓÒâ´óÀûÓïµÈ¡£ ×£Äú½ÚÈÕÓä¿ì£¬ÍòÊÂÈçÒ⣡ ±±¾©¶«·½Óïͨ·ÒëÖÐÐÄ µç»°£º010-62987225£¬13910430340 µç×ÓÓʼþ£º[EMAIL PROTECTED], [EMAIL PROTECTED] Http: www.east-trans.com ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: Bug: Name keyword expansion
Hi, Uwe! * Uwe Hamburger [EMAIL PROTECTED] [2002-03-07 15:15]: When updating a File (with options: retrieve tag) which is already local with the correct revision, the keyword 'Name' is not expanded. See http://www.cvshome.org/docs/manual/cvs_12.html#SEC98 for a description when $Name$ is expanded. (While this section only mentions cvs checkout, it applies to cvs export, too.) Regards Ingolf -- Ingolf Steinbach Jena-Optronik GmbH [EMAIL PROTECTED] ++49 3641 200-147 PGP: 0x7B3B5661 213C 828E 0C92 16B5 05D0 4D5B A324 EC04 ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
GISGPSRS
2002±±¾©¹ú¼Ê3S£¨GIS¡¢GPS¡¢RS£©¼¼ÊõÑÐÌÖôßչʾ»áThe 2rd Beijing International 3S Technical Symposium The 4rd Beijing International GIS Symposium and Exhibition »áÒéµØµã£º±±¾©Î÷½¼±ö¹Ý£¨º£µíÇøÎåµÀ¿ÚÍõׯ·18ºÅ£© ±¨µ½Ê±¼ä£º2002Äê4ÔÂ1ÈÕ ²¼Õ¹Ê±¼ä£º4ÔÂ1ÈÕ »áÒéÕ¹ÀÀʱ¼ä£º4ÔÂ2ÈÕ¡ª 4ÈÕ À뿪ʱ¼ä£º4ÔÂ5ÈÕÉÏÎç 3SµÄÓ¦ÓÃÇ°¾°£ºÔÚδÀ´¼¸ÄêÄÚ£¬µØÀí¿Õ¼äÐÅÏ¢(3S)½«ÊµÏÖËæʱ(anytime)ËæµØ(anywhere)ΪËùÓеÄÈË(anybody)ºÍÊÂ(anything)Ìṩʵʱ·þÎñ(4A·þÎñ)¡£ É3SµÄ´«Í³Ó¦Óà ¿ªÍØ3SеÄÓ¦Óà ÓÃÐÂ˼·½¨ÉèÊý×Ö³ÇÊÐ È«ÃæÌáÉýÖйúÐÅÏ¢»¯Ë®Æ½ÈëÊÀ¼°Éê°Â³É¹¦½«È«ÃæÌáÉýÊý×ÖÖйú½¨Éè ÑûÇ뺯 ÄúÄÜÏëÏóÔÚ²»¾ÃµÄ½«À´£¨Ò²Ðí¾ÍÔÚÃ÷Ä꣩£¬ÄúÖ»ÐèÒªÒ»¸öÊÖ»ú¡¢Ò»¿é±í»òÆäËüËæÉíСÎï¼þ¾Í¿ÉÒÔ׼ȷ¶¨Î»ÓÚ¸ßÂ¥´óÏÃÖ®¼ä»ò´Ôɽ¾þÁëÖ®µß£¬ÏíÊÜ3S¼¼Êõ´øÀ´µÄȫй¤×÷ÓëÉú»î±ãÀû£¿ ÄúΪÄúµ¥Î»ÐÅÏ¢»¯Ë®Æ½µÍ¡¢Ê¼ÖÕÕÒ²»µ½·¢Õ¹Ö®Â·¶øÀ§»óÂ𣿽¨Á¢ÍøÕ¾¡¢¼òµ¥µÄµç×ÓÉÌÎñ²»ÊÇÐÅÏ¢»¯Ö®±¾£¬È«ÃæÓ¦ÓÃ3S¼¼Êõ½«Õ¼ÁìÐÅÏ¢¼¼ÊõµÄÖƸߵ㡣 Äúµ¥Î»Îª½«À´µÄ·¢Õ¹×öºÃ×¼±¸ÁËÂð£¿ÔÚÇ¿µ÷¿ì½ÝÓë¸ßЧ·þÎñµÄ½ñÌ죬ÔÚÏû·ÑÕßÔ½À´Ô½Ç¿µ÷·þÎñµÄ½ñÌ죬ÔÚÒ»ÇÐÒÔÓû§²»¶Ï±ä»¯µÄÐèÇóÓë·þÎñΪ¾ÓªÖ®±¾µÄÃ÷Ì죬ÄúÖªµÀ3S½«·¢»ÓʲôÖØÒªµÄ×÷ÓÃÂ𣿠Äú¹«Ë¾ÕÒ²»µ½ÀûÈóÔö³¤µã£¬²»ÖªÖг¤ÆÚ¿ÉÄܳöÏÖµÄÈ«Éç»á¶¼¹Ø×¢²¢ÕùÏàÓ¦ÓõÄм¼ÊõÈȵ㣿ÄÇôÇëÏÖÔÚͶÉí3S¼¼ÊõµÄ¿ª·¢ÓëÓ¦ÓᣠÄú×öºÃ×¼±¸ÓÚ2002Äê3ÔÂ31ÈÕÆð³ÌÀ´±±¾©²Î»áÁËÂ𣿠Ö÷°ìµ¥Î» ²â»æÒ£¸ÐÐÅÏ¢¹¤³Ì¹ú¼ÒÖصãʵÑéÊÒ ÖпÆÔº×ÊÔ´Óë»·¾³ÐÅϢϵͳ¹ú¼ÒÖصãʵÑéÊÒ ¹ú¼ÒÒ£¸ÐÓ¦Óù¤³Ì¼¼ÊõÑо¿ÖÐÐÄ ¹ú¼ÒGPSÓ¦Óù¤³Ì¼¼ÊõÑо¿ÖÐÐÄ ±±¾©´óѧң¸ÐÓëGISÑо¿Ëù Öйúº£ÍâµØÀíÐÅÏ¢ÏµÍ³Ð»á ¹ú¼ÊÉãÓ°²âÁ¿ÓëÒ£¸Ðлá°îÁªÊý¾Ý¿âÓ뻥²Ù×÷¹¤×÷×é ¹ú¼ÊÉãÓ°²âÁ¿ÓëÒ£¸Ðлá¿Õ¼äÊý¾Ý¹ÜÀí¼¯³Éϵͳ¹¤×÷×é Ö§³Öµ¥Î» ¹ú¼ÒÏà¹Ø²¿Î¯ÐÅÏ¢ÖÐÐÄ ²¿·ÖÊ¡ÊÐÐÅÏ¢°ì Ïà¹Ø¹æ»®²â»æÔºµÈÊ®¼¸¼Òµ¥Î» ³Ð°ìµ¥Î» ±±¾©Ã÷ÈÕ²ÊÔƹã¸æÓÐÏÞ¹«Ë¾ ÌرðÖ§³ÖýÌå ¡¶3SÊÀ½ç¡· ÄúÁ˽â3SÈçºÎÌáÉý´«Í³ÐÐÒµÂ𣿠ÄúÀ´×ÔÓÚ×ÔÀ´Ë®¡¢µçÁ¦¡¢ÃºÆøµÈÐÐÒµ£¬ÄúÖªµÀGISÈçºÎ¿ì½Ý׼ȷ¶¨Î»¹ÜµÀ¡¢¹ÜÏß¹ÊÕÏÂð£¿ÄúÖªµÀ3SÈçºÎ×ö¹ÜÏßÑ¡ÐÍÓÅ»¯£¬¸üÓÐЧÌá¸ß¹ÜÀíÄÜÁ¦Â𣿠ÄúÀ´×ÔÓÚ¹úÍÁ¡¢½»Í¨¡¢Ë®µç¡¢¼Æί¡¢²â»æ¡¢µçÐŵÈÐÐÒµ¹ÜÀí»ú¹Ø£¬ÄúÁ˽â3S¼¼ÊõÏÖÔÚÒÑÈÕÐÂÔÂÒƵط¢Õ¹ÁËÂð£¿ÄúÖªµÀ²ÉÓÃ3S¼¼Êõ½«²úÉúʲô±ä»¯Â𣿠ÄúÀ´×Ô3S´«Í³Ó¦Óõĵؿ󡢿±Ì½µÈ²¿ÃÅ£¬ÄúÁ˽â3SµÄ¸üÐÂÌæ´ú²úÆ·¡¢×îз¢Õ¹ÏÖ×´¼°ÈçºÎ½â¾öÄúʹÓÃÖеÄÎÊÌâÂ𣿠ֻÓи÷µ¥Î»¸÷ÐÐÒµÆëÐÄÐÁ¦£¬Êý×ÖÖйú½¨Éè²Å²»½ö½öÊǿںš£ Äúµ¥Î»ÍÏÑÓÖйúÊý×Ö»¯½¨ÉèµÄ½ø³ÌÁËÂ𣿠¸üйÛÄ´ÓÏÖÔÚ×öÆð£¬Âõ¿ªÒ»²½º£À«Ìì¿Õ¡£ ¿ìÀ´±¨Ãû²Î»á°É£¬±¾´Î»áÕ¹´ø¸øÄúµÄ²»½ö½öÊÇѧϰÓë½»Á÷¡£ 3SÇé¿ö½éÉÜ Êý×ÖµØÇòµÄ¸ÅÄîÊÇËÄÄêÇ°ÓÉÃÀ¹úÇ°¸±×Üͳ¸ê¶ûÌá³öµÄ¡£Êý×ÖµØÇòÖ÷ÒªÖ¸Ó¦ÓõØÀíÐÅϢϵͳ£¨GIS£©¡¢È«Çò¶¨Î»ÏµÍ³£¨GPS£©¡¢Ò£¸Ð£¨RS£©µÈ¼¼Êõ£¬ÒÔÊý×ֵķ½Ê½»ñÈ¡¡¢´¦ÀíºÍÓ¦ÓùØÓÚµØÇò×ÔÈ»ºÍÈËÎÄÒòËصĿռäÊý¾Ý£¬²¢ÔÚ´Ë»ù´¡ÉϽâ¾öÈ«Çò¸÷ÖÖÎÊÌâ¡£Èç½ñ£¬ÐÅÏ¢¼¼Êõ¸ïÃüϯ¾íÈ«Çò£¬Ê¹ÈËÀà¶ÔµØÇò¿Õ¼äÊý¾Ý½øÐд¦Àí¡¢·ÖÎöµÄ¼¼ÊõÊֶκ͹ÛÄî·¢ÉúÁË·Ì츲µØµÄ±ä»¯¡£ÔÚÕâÖÖÇé¿öÏ£¬ÈËÃÇ¿ÉÒÔ°ÑÓйصØÇòµÄ´óÁ¿µÄ¡¢¶à·Ö±æÂʵġ¢ÈýάµÄ¡¢¶¯Ì¬µÄÊý¾Ý°´µØÀí×ø±ê¼¯³ÉÆðÀ´£¬ÐγÉÒ»¸öÊý×ÖµØÇò¡£½èÖúÓÚÕâ¸öÊý×ÖµØÇò£¬ÈËÃÇÎÞÂÛ×ßµ½ÄÄÀ¶¼¿ÉÒÔ°´µØÀí×ø±êÁ˽âµØÇòÉÏÈκÎÒ»´¦¡¢Èκη½ÃæµÄÐÅÏ¢¡£Êý×ÖµØÇòÊǶÔÕæʵµØÇò¼°ÆäÏà¹ØÏÖÏóͳһÐÔµÄÊý×Ö»¯ÖØÏÖºÍÈÏʶ£¬ºËÐÄ˼ÏëÓÐÁ½µã£ºÒ»ÊÇÓÃÊý×Ö»¯ÊÖ¶ÎͳһµØ´¦ÀíµØÇòÎÊÌ⣻¶þÊÇ×î´óÏ޶ȵØÀûÓÃÐÅÏ¢×ÊÔ´¡£Êý×ÖµØÇòÓÉÏÂÁÐÌåϵ¹¹³É£ºÊý¾Ý»ñÈ¡Óë¸üÐÂÌåϵ¡¢Êý¾Ý´¦ÀíÓë´æ´¢Ìåϵ¡¢ÐÅÏ¢ÌáÈ¡Óë·ÖÎöÌåϵ¡¢Êý¾ÝÓëÐÅÏ¢´«²¥Ìåϵ¡¢Êý¾Ý¿âÌåϵ¡¢ÍøÂçÌåϵ¡¢×¨ÓÃÈí¼þÌåϵµÈ¡£Êý×ÖµØÇò¿ÉÒÔ°üÈÝ80£¥ÒÔÉϵÄÈËÀàÐÅÏ¢×ÊÔ´£¬ÊÇδÀ´ÐÅÏ¢×ÊÔ´µÄÖ÷ÌåºËÐÄ¡£ ½ü¼¸ÄêÀ´£¬È«ÇòÊý×Ö»¯È¡µÃÁËÍ»·ÉÃͽøµÄ·¢Õ¹¡£ÔÚÈ«ÇòÐÅÏ¢Êý×Ö»¯µÄʵʩ¹ý³ÌÖУ¬µØÇò¿Õ¼äÐÅÏ¢¼¼Êõ£¨3S,¼´GIS¡¢GPS¡¢RS£©Æð×ÅÊ®·ÖÖØÒªµÄ×÷Óã¬GIS¡¢RS¡¢GPSµÄ¼¯³É¹¹¼ÜÁËÊý×ÖµØÇò¡£1999Äê11ÔÂ19ÈÕ£¬ÔÚ±±¾©ÕÙ¿ªÁË¡°Êý×ÖµØÇò¹ú¼Ê»áÒ顱£¬ Àîá°Ç帱×ÜÀíÔÚ»áÉÏÌá³ö£¬Öйú½«Á¦ÕùÔÚÊý×ÖµØÇò½¨ÉèÖÐʵÏÖ¿çԽʽ·¢Õ¹¡£ µØÀíÐÅϢϵͳ£¨Geographical Information System,GIS£©Êǽü¶þÊ®ÄêÀ´·¢Õ¹ÆðÀ´µÄÒ»ÃÅ×ÛºÏÓ¦ÓÃϵͳ£¬ËüÄܰѸ÷ÖÖÐÅϢͬµØÀíλÖúÍÓйصÄÊÓͼ½áºÏÆðÀ´£¬²¢°ÑµØÀíѧ¡¢¼¸ºÎѧ¡¢¼ÆËã»ú¿Æѧ¼°¸÷ÖÖÓ¦ÓöÔÏó¡¢Internet¡¢¶àýÌå¼¼Êõ¼°ÐéÄâÏÖʵ¼¼ÊõµÈÈÚΪһÌ壬ÀûÓüÆËã»úͼÐÎÓëÊý¾Ý¿â¼¼ÊõÀ´²É¼¯¡¢´æ´¢¡¢±à¼¡¢ÏÔʾ¡¢×ª»»¡¢·ÖÎöºÍÊä³öµØÀíͼÐμ°ÆäÊôÐÔÊý¾Ý¡£ÕâÑù£¬¾Í¿É¸ù¾ÝÓû§ÐèÒª½«ÕâЩÐÅϢͼÎIJ¢Ã¯µØÊäË͸øÓû§£¬±ãÓÚʹÓᣠȫÇò¶¨Î»ÏµÍ³£¨Global Positioning System,GPS£©ÊÇÉÏÊÀ¼Í70Äê´úÓÉÃÀ¹ú¹ú·À²¿Åú×¼£¬Â½º£¿ÕÈý¾üÁªºÏÑÐÖƵÄÐÂÒ»´ú¿Õ¼äÎÀÐǵ¼º½¶¨Î»ÏµÍ³¡£ÆäÖ÷ҪĿµÄÊÇΪ½¡¢º£¡¢¿ÕÈý´óÁìÓòÌṩʵʱ¡¢È«ÌìºòºÍÈ«ÇòÐԵĵ¼º½·þÎñ¡£È«Çò¶¨Î»ÏµÍ³¹²ÓÉÈý²¿·Ö¹¹³É£ºµØÃæ¿ØÖƲ¿·Ö¡¢¿Õ¼ä²¿·Ö¡¢Óû§×°Öò¿·ÖµÈ¡£GPSµÄÖ÷ÒªÌصãÊÇÈ«Ììºò¡¢È«Çò¸²¸Ç¡¢Èýά¶¨ËÙ¶¨Ê±¸ß¾«¶È¡¢¿ìËÙʡʱ¸ßЧÂʼ°Ó¦Óù㷺¶à¹¦ÄÜ¡£ Ò£¸Ð(Remote Sensing,RS)£¬¹ËÃû˼Ò壬¾ÍÊÇÒ£Ô¶µØ¸ÐÖª¡£ÈËÀàͨ¹ý´óÁ¿µÄʵ¼ù£¬·¢ÏÖµØÇòÉÏÿһ¸öÎïÌ嶼ÔÚ²»Í£µØÎüÊÕ¡¢·¢ÉäºÍ·´ÉäÐÅÏ¢ºÍÄÜÁ¿£¬ÆäÖÐÓÐÒ»ÖÖÈËÀàÒѾÈÏʶµ½µÄÐÎʽ¡ª¡ªµç´Å²¨£¬²¢ÇÒ·¢ÏÖ²»Í¬ÎïÌåµÄµç´Å²¨ÌØÐÔÊDz»Í¬µÄ¡£Ò£¸Ð¾ÍÊǸù¾ÝÕâ¸öÔÀíÀ´Ì½²âµØ±íÎïÌå¶Ôµç´Å²¨µÄ·´ÉäºÍÆä·¢ÉäµÄµç´Å²¨£¬´Ó¶øÌáÈ¡ÕâЩÎïÌåµÄÐÅÏ¢£¬Íê³ÉÔ¶¾àÀëʶ±ðÎïÌå¡£ Ò£¸ÐµÄʵÏÖ»¹ÐèÒªÒ£¸Ðƽ̨£¬ÏñÎÀÐÇ¡¢·É»ú¡¢ÆøÇòµÈ£¬ËüÃǵÄ×÷ÓþÍÊÇÎȶ¨µØÔËÔØ´«¸ÐÆ÷¡£µ±ÔÚµØÃæÊÔÑéʱ£¬»¹»áÓõ½µØÃæÏóÈý½Ç¼ÜÕâÑù¼òµ¥µÄÒ£¸Ðƽ̨¡£Õë¶Ô²»Í¬µÄÓ¦ÓúͲ¨¶Î·¶Î§£¬ÈËÃÇÒѾÑо¿³öºÜ¶àÖÖ´«¸ÐÆ÷£¬Ì½²âºÍ½ÓÊÕÎïÌåÔڿɼû¹â¡¢ºìÍâÏߺÍ΢²¨·¶Î§Äڵĵç´Å·øÉä¡£´«¸ÐÆ÷»á°ÑÕâЩµç´Å·øÉä°´ÕÕÒ»¶¨µÄ¹æÂÉת»»ÎªÔʼͼÏñ¡£ÔʼͼÏñ±»µØÃæÕ¾½ÓÊÕºó£¬Òª¾¹ýһϵÁи´ÔӵĴ¦Àí£¬²ÅÄÜÌṩ¸ø²»Í¬µÄÓû§Ê¹Óá£
¿Ü·Î¿òÀ» ´Þ·¡µå¸±²²¿ä (¼ºÀÎ-±¤°í)
¿Ü·Î¿òÀ» ´Þ·¡ÁÙ ¾ÖÀÎÀÌ ÇÊ¿äÇÒ¶§ 24½Ã°£ ±â´Ù¸®°í ÀÖ¾î¿ä 1. Àüȱ⸦ µé°í 060-707-7749 ¸¦ ´©¸£¼¼¿ä. (Àü±¹½Ã³»¿ä±Ý) °¡ÀÔºñ ¾ø½¿ 2. ¿Ü·Î¿òÀ» ´Þ·¡ÁÙ ´ëÈ»ó´ë°¡ ÇÊ¿äÇϽźÐ. 3. Áö±Ý Àüȸ¦ µé°í 060-707-7749¸¦ ´·¯ÁÖ¼¼¿ä 5. °¡ÀÔÈÄ °ø°³°Ô½ÃÆÇ¿¡ ÀÚ½ÅÀÇ °³ÀÎÇÁ·ÎÇÊÀ» °·ÂÇÏ°Ô ¾îÇÊÇغ¸¼¼¿ä ±×´ÙÀ½¿¡ ¹«½¼ÀÏÀÌ ÀϾÁö Ã¥ÀÓ¸øÁ® ** ÀÌÄÉÇÏ¸é ¿Àºü¾ß Ç°À¸·Î ¿³ª¼½¾¯ ÂßÂß»§»§ ¾ð³ÄµéÀÌ È£¹Ú³ÕÄðó·³ ¿ì·ç·è!! ** º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø¹ý ±ÔÁ¤¿¡ µû¶ó ±¤°í¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç ¼ö½Å°ÅºÎÀåÄ¡¸¦ ¸¶·ÃÇÏ°í ÀÖ½À´Ï´Ù. º» ¸ÞÀÏÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ¼öÁýÇÑ°ÍÀÌ¸ç ¸ÞÀÏÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎÁ¤º¸µµ °®°í ÀÖÁö ¾Ê½À´Ï´Ù ¿øÄ¡ ¾ÊÀº Á¤º¸¿´´Ù¸é Á¤ÁßÈ÷ »ç°ú µå¸®¸ç, ¼ö½Å°ÅºÎ¸¦ ÇØ ÁÖ½Ã¸é ´ÙÀ½ºÎÅÍ´Â ¸ÞÀÏÀÌ ¹ß¼ÛµÇÁö ¾ÊÀ» °ÍÀÔ´Ï´Ù ¼ö½Å°ÅºÎ ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
Michael Sterrett -Mr. Bones.- writes: It would be nice to receive some comment from the CVS development team. This is the third time I've sent this out the the mailing lists with not a peep from anyone about it. Very disappointing. contrib/README: Unsupported also means that no one has volunteered to accept and check in changes to this directory. So submissions for new scripts to add here are unlikely to be accepted. Suggested changes to the existing scripts here conceivably might, but that isn't clear either, unless of course they come from the original author of the script. If you have some software that works with CVS that you wish to offer it is suggested that you make it available by FTP or HTTP and then announce it on the info-cvs mailing list. -Larry Jones You can never really enjoy Sundays because in the back of your mind you know you have to go to school the next day. -- Calvin ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
On Thu, 7 Mar 2002, Larry Jones wrote: contrib/README: Unsupported also means that no one has volunteered to accept and check in changes to this directory. So submissions for new scripts to add here are unlikely to be accepted. Suggested changes to the existing scripts here conceivably might, but that isn't clear either, unless of course they come from the original author of the script. If you have some software that works with CVS that you wish to offer it is suggested that you make it available by FTP or HTTP and then announce it on the info-cvs mailing list. -Larry Jones Larry -- Thanks for the response. I guess I'm just a little naive when it comes to the development process of CVS. I assumed that any sort of improvement to the distribution would be welcome. In my involvement in open source projects in the past, the maintainers of the projects have been very receptive and pleased to receive code, which they didn't have to write. I see a problem with the CVS code as distributed. That is, it has a single csh script which is both slow and makes the CVS code-base depend on an additional unix utility when it doesn't have to. I believe I addressed both of these problems with my re-write of the script in perl. I've announced it on the info-cvs list (a couple of times now) and I'd like to make it available via FTP in the CVS distribution if I could just get some cooperation from you, Derek or one of the other silent CVS developers. Thanks, Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
Hi Michael. Hi Riley -- Thanks for the reply. At least now I know that my mail is being seen by someone other than myself. NP. Let me address your points at they go... I'm not on the CVS development team as such, just being a very happy user of CVS... Oh, don't be fooled -- I'm a very happy user of CVS too. I just use SCCS in my day job because that's what we've always used, but that's changing these days -- mostly with the help of the sccs2rcs perl script that I included before. As stated in my original email, I never managed to get on with SCCS on the only occasion I was expected to use it, so can't really comment on it in any sort of meaningful way... ...but I would like to offer one possible reason for the lack of comments: Perhaps those on the list here are like me and don't use SCCS in the first place, so have no use for the script. True, that could be a reason, but you may be missing the fact that I'm not advocating the *addition* of a script, but a *replacement* of a script. If you think about it, you'll soon realise that the difference you refer to is irrelevant to anybody who doesn't use SCCS - if they don't use SCCS, then they will have no interest whatsoever in the existence of a script to convert from SCCS to CVS, much less in how well (or even whether) the script in question works. If you check your CVS distribution, you'll find in the contrib directory a sccs2rcs script *already* there. However, it is written in csh which is A) slow B) one more dependency for your .deb or .rpm to depend on. The perl script that I'm requesting consideration addresses both of these issues since the perl script runs about twice as fast as the csh version and, since there are already perl scripts in the CVS distribution, adds *no* additional dependencies. To get any comments on either your script or the original one, you'd need to find somebody else who uses both SCCS and CVS and needs to convert from SCCS to CVS. Other than that, to be honest, nobody's going to be interested for the simple reason that they've no reasonable means to test either script. Another possibility is the length of the To: and CC: list in your email - I know several people who have their system set up to auto-kill any emails with more than three names in those two combined simply as a way to cut down the amount of mail they have to handle, and your email would not have made it to any of them. I have sent this email already twice before -- once to bug-cvs and once to user-cvs with very reasonable To: and CC: lines so I don't think this is the reason. I'm on the bug-cvs list but not on the user-cvs list, and I've never seen your email before the one I replied to. I've been on the bug-cvs list since last September, so wouldn't have seen it if posted before then, but if posted since, it apparently didn't get through to that list, which could explain the lack of response... I've also written to Larry Jones (who seems to be the primary person committing to the CVS source tree) directly and I got *no* reply - not even a go away or not interested! That much I can't comment on as I don't know Larry's circumstances. However, if they're anything like me, he probably doesn't have the time to even read, much less reply to, emails about things he's not directly interested in. To put that in context, allow that (after my spam-filter has finished with them) I receive between 500 and 700 emails a day, mostly from the Linux-Kernel or the UK-Genealogy mailing lists, and if I even read every email I received, I'd have little time to do anything else. As it happens, I read every mail posted to the Linux-8086, Linux-Hams and Bug-CVS mailing lists, but I only reply to ones where I can make a positive contribution of some sort. With most of the mailing lists I receive, I decide whether to read a particular email based on (a) the sender is somebody important on that list (I read EVERY email from either Linus Torvalds or Alan Cox on the Linux-Kernel list), or (b) the subject line catches my attention. If neither of those apply, the email doesn't get read - it's as simple as that. Best wishes from Riley. ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
On Thu, 7 Mar 2002, Larry Jones wrote: Anybody with sccs, CVS, make, and perl almost certainly already has csh, Well, I don't - at least, I wouldn't if I didn't have to because CVS depends on csh *only* because of the sccs2rcs csh script. I'd love to remove csh from my system, but that would break dependencies (which is primarily why I re-wrote it in the first place). chop And given the stunning lack of interest shown here, it seems that no one really cares. So, while I'm sure you think it's wonderful and it sounds like it was a big benefit to you, I don't any value to adding it to the CVS distribution. Ok, let me try another idea on you then. Given the stunning lack of interest which, I admit certainly seems evident, how would you feel about removing the sccs2rcs script from the CVS distribution? That'd make me just as happy. All future CVS distribution gets smaller and you won't have to deal with any future bugs in the sccs2rcs script (which I see you had to patch a couple of times in the last year) -- everybody comes out a winner. Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
[ On Thursday, March 7, 2002 at 16:46:04 (-0500), Michael Sterrett -Mr. Bones.- wrote: ] Subject: Re: sccs2rcs to perl I see a problem with the CVS code as distributed. That is, it has a single csh script which is both slow and makes the CVS code-base depend on an additional unix utility when it doesn't have to. Well, it's only a contributed utility, not a core part of the CVS code as distributed. I believe I addressed both of these problems with my re-write of the script in perl. No, you did not. Only a translation to POSIX Shell or C would have addressed both problems. While the translation to perl may have made the script run faster, it only changed the reliance on one semi-standard tool to another less standard tool (perl is neither commonly available on all unix platforms, nor is it terribly small and fast, though it may be faster than csh). -- Greg A. Woods +1 416 218-0098; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
On Thu, 7 Mar 2002, Greg A. Woods wrote: [ On Thursday, March 7, 2002 at 16:46:04 (-0500), Michael Sterrett -Mr. Bones$ Subject: Re: sccs2rcs to perl I see a problem with the CVS code as distributed. That is, it has a single csh script which is both slow and makes the CVS code-base depend on an additional unix utility when it doesn't have to. Well, it's only a contributed utility, not a core part of the CVS code as distributed. All the Linux distributions I have access too include sccs2rcs as part of the CVS package because it is distributed as part of the CVS tar ball. Because of that, I consider it part of CVS. I believe I addressed both of these problems with my re-write of the script in perl. No, you did not. Only a translation to POSIX Shell or C would have addressed both problems. Sorry, but I disagree. There are already a number of perl scripts in the contrib directory so the package as a whole depends on perl already. I don't think you can argue that I've not reduced the number of dependencies for the CVS package. Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
[ On Thursday, March 7, 2002 at 17:21:08 (-0500), Michael Sterrett -Mr. Bones.- wrote: ] Subject: Re: sccs2rcs to perl Well, I don't - at least, I wouldn't if I didn't have to because CVS depends on csh *only* because of the sccs2rcs csh script. I'd love to remove csh from my system, but that would break dependencies (which is primarily why I re-wrote it in the first place). I removed csh from almost all of my systems long ago. I still have no interest in re-writing sccs2rcs into perl though :-) (I don't think I would ever use sccs2rcs.csh either -- I'd write my own conversion tool in POSIX shell if I had to, even though it would be trivial for me to either install csh again or find a machine where it is still present and working) Ok, let me try another idea on you then. Given the stunning lack of interest which, I admit certainly seems evident, how would you feel about removing the sccs2rcs script from the CVS distribution? That'd make me just as happy. All future CVS distribution gets smaller and you won't have to deal with any future bugs in the sccs2rcs script (which I see you had to patch a couple of times in the last year) -- everybody comes out a winner. I wouldn't have any objection to that! ;-) -- Greg A. Woods +1 416 218-0098; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
[ On Thursday, March 7, 2002 at 18:06:22 (-0500), Michael Sterrett -Mr. Bones.- wrote: ] Subject: Re: sccs2rcs to perl All the Linux distributions I have access too include sccs2rcs as part of the CVS package because it is distributed as part of the CVS tar ball. Because of that, I consider it part of CVS. Unless you have SCCS files you wouldn't even know about it -- it's hardly a part of CVS, especially since it's explicitly only included in the contrib sub-directory. Sorry, but I disagree. There are already a number of perl scripts in the contrib directory so the package as a whole depends on perl already. That's also irrelevant. You need to consider that the things in the contrib subdirectory are individual stand-alone things -- not related to each other (well, there are some that are related to each other, but most are completly independent), and only minimally related to CVS (sccs2rcs is only related very indirectly in that the RCS files it creates can be used by CVS). CVS itself, as a whole, does not depend on perl in any what whatsoever. I don't think you can argue that I've not reduced the number of dependencies for the CVS package. The contrib things are not really a part of the CVS package -- they're just a collection of things that were contributed but explicitly _not_ added to the package proper. -- Greg A. Woods +1 416 218-0098; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
On Thu, 7 Mar 2002, Greg A. Woods wrote: I removed csh from almost all of my systems long ago. Ah, I envy you. :-) I refuse to ignore the package dependencies on my systems though... I still have no interest in re-writing sccs2rcs into perl though :-) Well, I did it for two reasons: 1. the package dependencies (which I guess you don't mind ;-)) 2. I have a bunch of SCCS directories I need to convert to RCS and the csh version of the script is way too slow. (I don't think I would ever use sccs2rcs.csh either -- I'd write my own conversion tool in POSIX shell if I had to, even though it would be trivial for me to either install csh again or find a machine where it is still present and working) Ah, someone who dislikes csh even more than I do. Chop my suggestion that sccs2rcs be removed from the cvs distribution I wouldn't have any objection to that! ;-) Great! Two votes for... Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
Re: sccs2rcs to perl
[ On Thursday, March 7, 2002 at 18:40:03 (-0500), Michael Sterrett -Mr. Bones.- wrote: ] Subject: Re: sccs2rcs to perl 2. I have a bunch of SCCS directories I need to convert to RCS and the csh version of the script is way too slow. Is? was? :-) Why convert from SCCS? I don't have any larger projects managed by SCCS, but for all the small ones I have there's not much point to changing over to RCS (or CVS) -- I just keep using SCCS :-) -- Greg A. Woods +1 416 218-0098; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
