We did not have the level of wanton ignorance and denial of evolution that we have now. Back then, I wouldn't have believed you if you told me that half the country turned out to be so stupid.

In a crate at least.

What the hell are you guys talking about? Flashes and rotating?

I think we're being trolled.

Exactly and you can control where it goes by wiggling your ass.

two sheets versus a couple of giant wads? You're definitely reducing your TP usage.

a sheet of TP or drip dry.

Its is relevant in a bass ackwards way. It shows that gender is innate and not a social construct based on how you were raised. Of course the logical conclusion is the exact opposite of what the OP guy believes.

Can you imagine the harm that would have happened if he just so happened to be transgender?

Age to drive: 16? Still a teenager Age of consent: varies by state but is generally around 15 or so. Smoke: gross. But I never heard of a teenager having much problems acquiring tobacco, alcohol, or weed.

That is exactly what gender affirming care for youths is. Its basically staving off puberty until they are old enough to determine that they really do want medical transisition.

You managed to agree with me without understanding the discussion.

Lets say you run a build that compiles v2.0 branch and store the artifacts as myproduct-2.0.2.tar.gz

You deploy that to your QA environment. Your testers have it and when they are done the results "looks good, time to release it to prod.

What you should do is take your build an promote it to released status. Now this can be picked up by customers or deployed to prod.

But, believe it not, there are people that branches named dev, test, prod. So when they complete testing on the artifacts above, they run another build on the prod branch and either release that to customers or deploy on internal prod.

You're saying the same thing as me -- when they do that prod build, its not the same artifacts as they tested in QA. In fact, anything you tested previously is no longer relevant because you have a new build.

You shouldn’t be able to rerun the same build with different results

All it takes is a compiler embedding a timestamp somewhere in the output. You are aware that repeated builds is a pretty big effort right? In fact Fedora 41 has a change to make sure rpm builds are reproducible: https://fedoraproject.org/wiki/Releases/41/ChangeSet#Reproducible_Package_Builds

Since you brought an OS package manager into the discussion (which wasn't what I thought was being discussed), let's look at from a fedora/rpm perspective. All I'm saying is that after building an rpm they push it through the pipeline. It goes to updates-testing and then later updates. The exact same rpm is promoted to updates from updates-testing. They do not build a new rpm for updates repo.

I see many people who have separate builds for each environment.

I guess we disagree on that one.

There are a lot of things sold unrefrigersted that need to refrigerated after opening. Like every jar of spaghetti sauce I've ever bought.

Too lazy to just store them in sealed plastic bags?

I have peanut butter in the fridge. I hate PB and it's only used for my dogs kong. Fridge firms it up and keeps the oil from separating. Much easier to work with than when it's room temp and runny.

Those are all normal things to refrigerste. Except kimchi possibly as I've never had it in my house.

You're not going to enjoy dethawed bread if it formed crystals in the freezer. The only option is to toast it.