Held files on PT

[Max Martin Richter]

Dear all,
everytime I scroll through the parts containing a hold vote, I'm frustrated cause there are so many unused primitives, that sit there for months and years.

Therefore I would like to suggest, that all unused primitives containing a hold vote should get deleted 6 months after both states got true.

/Max

[Steffen]

I don't understand the question:
if the primitive is unused, then why does it hurt that it sits on the PT being held?
Where does the frustration come from?
What thing or task or idea is being held up by the primitive sitting there?
If a primitive carries a hold vote for an invalid reason, I think we should remove the hold vote then in that case instead.
Please help me understand...

[Gerald Lasser]

In my opinion, some can be deleted straight away, like those that were generated as "ring" but a "rin" one exists. I removed this primitive from the huge propellor part last week. SO there should be at least two which fall under this case.

On the other hand the primitives that are held, are not that many, I guess less than 30 files.

[Steffen]

the "ring" ones are the newer ones.

in the past we were forced to abbreviate it to "rin" due to the then-existing 8.3 filename limit.

that no longer exists, and we decided to go for the clearer name "ring".

if a "rin" file exists on the PT, it should be moved to "ring" AFAIK.

[Gerald Lasser]

the "ring" ones are the newer ones.

in the past we were forced to abbreviate it to "rin" due to the then-existing 8.3 filename limit.

that no longer exists, and we decided to go for the clearer name "ring".

if a "rin" file exists on the PT, it should be moved to "ring" AFAIK.

The ones I am referring to are:

on PT: p/48/1-4ring15.dat  -> official already: p/48/1-4rin15.dat
on PT: p/48/1-4ring21.dat  -> official already: p/48/1-4rin21.dat


All parts that used those "ring" in the past are now using the existing hi-res prims "rin"

those can go immediately :-)

[Steffen]

what do you mean by "go"?

the official "rin" primitives need to become MOVED-TO's to the "ring" versions.

while on the PT, parts should be updated to use "ring" instead of "rin".

at least that's what I understood is our current strategy.

[Magnus Forsberg]

No, we don't replace, and create Move to, on official ring primitives using the old format. They were deemed to be to many and we decided not to renumber them.

New ring primitives must use the correct name "ring" .

What Gerald has found and eliminated, are a few parts, using a newly created ring-primitive, that could, and should have, used the older, allready existing rin-primitive.

[Steffen]

ah, understood.

I did not know of that decision up to now.

thanks for explaining.

[Gerald Lasser]

what do you mean by "go"?

that they can be deleted