à la con

  • 1 Post
  • 6 Comments
Joined 4 months ago
cake
Cake day: June 25th, 2024

help-circle

  • 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