Issue 3621 - neon/ is not tagged for OOO_STABLE_1
Summary: neon/ is not tagged for OOO_STABLE_1
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: sander_traveling
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-21 21:58 UTC by nickb
Modified: 2003-03-24 08:51 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description nickb 2002-03-21 21:58:41 UTC
If you pull OOO_STABLE_1 you get external/neon and not neon/.
eg:
nickb@dingo-sise/openoffice(STABLE_1):workarea 239% cvs co -rOOO_STABLE_1 neon
? neon/unxirgm.pro
cvs server: Updating neon
cvs server: neon/makefile.mk is no longer in the repository
cvs server: neon/neon.patch is no longer in the repository
cvs server: Updating neon/download
cvs server: neon/download/neon-0.14.0.tar.gz is no longer in the repository
cvs server: Updating neon/prj
cvs server: neon/prj/build.lst is no longer in the repository
cvs server: neon/prj/d.lst is no longer in the repository
nickb@dingo-sise/openoffice(STABLE_1):workarea 240% cvs co -rHEAD neon
? neon/unxirgm.pro
cvs server: Updating neon
U neon/makefile.mk
U neon/neon.patch
cvs server: Updating neon/download
U neon/download/neon-0.14.0.tar.gz
cvs server: Updating neon/prj
U neon/prj/build.lst
U neon/prj/d.lst
Comment 1 nickb 2002-03-21 21:59:47 UTC
Oh, and external/neon should be un-tagged from OOO_STABLE_1

Not 100% sure if this is the correct component, sorry if its not.

Thanks
Comment 2 nickb 2002-03-21 22:05:39 UTC
added keyword
Comment 3 nickb 2002-03-22 01:17:12 UTC
so external/prj/build.lst should also be updated so it does NOT include
external/neon
Comment 4 sander_traveling 2002-04-15 14:58:45 UTC
actually, it seems I was wrong when I said we should be using neon/
instead of external/neon - it was apparently a false memory carry-over
from having done 642b.
Comment 5 michael.bemmer 2003-03-24 08:37:42 UTC
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.
Comment 6 michael.bemmer 2003-03-24 08:51:47 UTC
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.