| |
> Actually, I'm thinking of the reverse situation - the subfile
> is certified, but the parent file is not certified. In this case,
> it would be sloppy to release the subfile before the part file
> is released.
Actually, I'd *much* prefer this response to the alternate (i.e., better this
than releasing the "main" file before its subfiles). To be honest, I see no
problem with pre-emptively releasing a "not yet used" subfile before its "main"
file. Think of it as being *very* prepared for the "main" file... ;-)
Thanks,
Franklin
|
|
Message has 1 Reply:
 | | Re: Numbers Report
|
| (...) Well, yes. No argument there. (...) And what if, after the subfile is pre-emptively released, we realize that the file is totally wrong, and must be scrapped? Or some other thing comes up? It's just sloppy to put out unused files, and I don't (...) (23 years ago, 19-Apr-02, to lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
| | Re: Numbers Report
|
| (...) Actually, I'm thinking of the reverse situation - the subfile is certified, but the parent file is not certified. In this case, it would be sloppy to release the subfile before the part file is released. Look at the horse files for an example (...) (23 years ago, 15-Apr-02, to lugnet.cad.dev.org.ldraw)
|
14 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
