there is a segment on German public TV if that’s any help https://www.zdf.de/dokumentation/zdfzeit/zdfzeit-tricks-der-lebensmittelindustrie-mit-sebastian-lege-104.html#xtor=CS5-95

(Starts at 13:15 min). from what i remember it shows the same pattern mentioned by other commenters. vegetable fats instead of milk, thickeners, stabilizers, artificial flavors.

maybe try grundstoff.net (German company). their stuff is rather plain but t-shirts are available in very heavy fabric. i like them but I’m not sure whether it’s any good for when you work out (i sweat a lot when I’m skating).

thanks for the tip. I’ll have a look at what they have

Okay, now its getting ridiculous. Just measured the leg opening of my current pair, its 17’'.

Browsing through their website, i noticed, that leg opening appear to vary with color, approx. 1". Then i thought, maybe, i try my luck in different european stored (spain, belgium, netherlands). Same pattern, but then i noticed that i still had a tab for the US store open. Apparently, fit also differ between countries.

E.g. 501 Style # 005013411 in the US

How it Fits

Regular Through The Thigh
Sits At Your Waist
Straight Leg
Front rise: 11 1/4",Knee: 17 1/2",Leg opening: 16",Measurements based on size 32

in Spain

How it Fits

501
Sits At Your Waist
Straight Leg
Front rise: 12 1/4''
Knee: 18 5/8''
Leg opening: 17''
Measurements based on size 32

I just want a pair of jeans ffs

thanks for your reply. the thing is: all 501 100% cotton i tried have a smallish leg opening although they are called “straight leg”. these work fine when worn with shoes but sit too high when worn with biker boots. the ones i try to find again have a wide enough leg opening to fit the boots and rest in the heel. it’s really weird. and they really are 501 not boot cut, i swear

thanks for the reply, but i think i got that. from the linked article:

For example, if you changed repo/packages/foo/CHANGELOG.json, when git was getting ready to do the push, it was generating a diff against repo/packages/bar/CHANGELOG.json! This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per file in some cases, and you can imagine in a repo our size, how that would be a problem.

but wouldn’t these erroneous diffs not show up in git diff? it seems that they were pushing (maybe automatically?)without inspecting the diffs first

maybe I’m missing something but wouldn’t this show up in a diff before pushing?