Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Ummmm ... duh? (Score 1) 352

by Wootery (#49357285) Attached to: Modern Cockpits: Harder To Invade But Easier To Lock Up

Of course, now when the pilot has to take a leak there is one less cabin crew, which I'm sure you can construct a scenario in which that's not a good idea.

The solution is right there in the summary: have a flight-attendant lurk in the cockpit.

I'm baffled that this wasn't mandatory. As others have mentioned: what if he passed-out, or had a heart-attack? It's painfully obvious there should never be just one crew-member locked in the cockpit.

Comment: Re: Centralized on GitHub! LOL! (Score 3, Informative) 113

With Git, you have a full copy of the repo just by virtue of having "checked out" a copy.

Quick nitpick: that would be a clone, not a checkout.

For the non-git-users among us:

git clone: copy that repository to my local file-system. (All branches are copied across. This is normally over ssh or https.)

git checkout: give me the specified branch. (Doesn't require use of the network.)

git fetch: update the local store of the repository to reflect the current state of the repository on the server.

The end of labor is to gain leisure.