cross-laced_cutout implications

BUR #7640 has been rejected.

create implication cross-laced_cutout -> cross-laced_clothes
create implication cross-laced_cutout -> clothing_cutout
create implication cross-laced_slit -> cross-laced_clothes

Straightforward.

I looked through the images that are tagged as cross-laced_cutout and most of them do not qualify for the clothing_cutout tag.

According to the cleavage_cutout wiki
A cutout is a hole or opening that closes at both the upper and lower edges, in the same layer of clothing.

iphn said:

I looked through the images that are tagged as cross-laced_cutout and most of them do not qualify for the clothing_cutout tag.

According to the cleavage_cutout wiki
A cutout is a hole or opening that closes at both the upper and lower edges, in the same layer of clothing.

So basically it's used on posts that should just be cross-laced clothes with v-neck instead of cutout. I'll fix what I can but help with gardening it would be appreciated.

I also found the cross-laced_slit tag which applies to many of the images instead.
I'll go through them and fix as many as I can.

Appreciated. Edited the BUR to include that as well.

Yes, please clean up cross-laced cutout, otherwise this can't be approved. There's way too many mistags.

Perhaps we should look into that a bit more?

According to the cleavage cutout wiki

A cutout is a hole or opening that closes at both the upper and lower edges, in the same layer of clothing.

I removed the part in cross-laced slit wiki that also mentioned the word "cutout" because I thought it might be confusing, and I tried googling for "clothing cutout" and I didn't find much about it.

Are we sure that only doing fixes to follow that original clause (which isn't very intuitive according to the many mistags under those tags), is the right thing?

This bulk update request is pending automatic rejection in 5 days.

This bulk update request has been rejected because it was not approved within 45 days.

The bulk update request #7640 (forum #198757) has been rejected by @DanbooruBot.