If I'm understanding you correctly, you can have both. If there are specific rebase types that you perform regularly, you can create aliases for them and give them whatever name is meaningful to you.
For example, I frequently use `jj up` to rebase the current branch on main. Likewise, `jj pop` rebases just the current commit (popping it from its current place). I even have a `jj ppop` - better name suggestions are welcome - which does this but for the parent commit.
I suspect that the once-off effort to write your own commands would take no longer than it would take to read the documentation if the commands already existed, but with the hopeful extra benefit of giving you a better understanding of how to use rebase for those once in six months weird requirements when they may arise.
But to be clear, I'm not suggesting you must or even should put in this effort if you have something that works for you. My reply is mostly so that anyone who comes across this discussion and sees Steve's mention of -A, -B, etc isn't scared off by them. Whilst they're always there for you, you can use the power it gives you but in the form of single function commands that don't require you to think.
---
For anyone wondering, the aliases I mentioned. These can be dropped in your jj config with `jj config edit --user`.
Or perhaps people will understand that this is a car with an abundance of sensors, and all sorts of data about what it "sees" (including actual camera footage) will be stored and used in this sort of litigation. At which point you're taking on a multi-billion company with a hugely vested interest in winning any legal challenges.
I'd say it's a far more like buying a lottery ticket. Good luck!
In my experience few merchants limit Apple Pay to the contactless limit (Tesco being a notable exception) but many of the times I’ve used Apple Pay for larger purchases the person helping me has been surprised that it worked.
It’s worth mentioning here that as long as long as you have a few seconds notice you can force your Face ID enabled iPhone to require a passcode the next time it’s unlocked.
This is no longer true for Series 8 and Ultra watches. What I’ve not found out is whether this true of any Apple Watch running watchOS 9 or just the latest models.
This is different to optimized battery charging. As of iOS 16 (in an as yet unreleased point version) Apple plans to add support for clean energy charging, which will charge your iPhone when the grid has a cleaner mix of energy. I think this is US only to begin with.
Do you mind elaborating on what seeds you’re referring to. Or just some pointers on what to search for or something. I’m ignorant to the history here but would like to learn more.
Would it not make sense to upgrade to the newest node they can afford to a longer lifespan more life out of their next node? It feels like picking the next-oldest node leaves them having to solve this issue again in the near future...
When you say a "Mac" display, what are you referring to? Apple sells exactly one display - the XDR - and its pricing is such that no one casually buys because their $300 external display isn't working correctly. I very much doubt that is their motivation; it's likely just a (possibly misguided) effort to keep the UI simpler.
If it’s any consolation, I find English pronunciation very difficult, and I’m a native speaker. It surprises me that in my thirties I still regularly encounter situations where I want to use a word and realise I’ve never heard it spoken before, so have no idea if the pronunciation I use in my head when reading it is correct.
I also often hear others mispronounce words; friends, colleagues, even on TV.
I guess my point is that if you’re mispronouncing English words you’re speaking it like a native!
> Such systems enable greatly reduced charging times, as long as they are using fast chargers capable of working at up to 270kW.
> It also allows for weight reduction, as less copper is needed in the electric system. Electric motors are much simpler than combustion engines in construction and at their core they have a rotor, which is driven by a changing magnetic field. To induce this field, electrical systems often use up to four times the amount of copper found in combustion engines; higher voltages reduces the need for large amounts of copper. This permits smaller motors, freeing space in the vehicle for batteries.
Agree completely, but I can tell you for many of them pirating a text book is beyond their means. To do so you need not only internet access, but the sophistication to find pirated text books, and THEN the means to print possibly hundreds of pages. There is a big difference between poverty in the West and in a place like South Africa. Just printing the text book would be prohibitively expensive.
As someone who grew up watching rugby and only got into football as an adult, I couldn't believe the amount of disrespect players show to officials. I think I spent the first two years constantly saying "in rugby this guy would have been sent off by now" on repeat...
I absolutely loathe micro USB. I am constantly having to throw away cables that are a few months old because they no longer reliably charge my devices (PS4 controllers, Fire tablets, Bose headphones), and that's with me buying the most reliable cables I can find (Anker). Micro USB really is terrible...
Can you say why you think this is the case? Matz has very much made performance a focus: they've continued to improve the Ruby VM and added JIT, for example. Likewise, many of the non-performance related improvements in recent Ruby version have immediately been useful to me as a Rubyist. I'm not sure what meaningless features you refer to, but I'd be interested in seeing them enumerated.
For example, I frequently use `jj up` to rebase the current branch on main. Likewise, `jj pop` rebases just the current commit (popping it from its current place). I even have a `jj ppop` - better name suggestions are welcome - which does this but for the parent commit.
I suspect that the once-off effort to write your own commands would take no longer than it would take to read the documentation if the commands already existed, but with the hopeful extra benefit of giving you a better understanding of how to use rebase for those once in six months weird requirements when they may arise.
But to be clear, I'm not suggesting you must or even should put in this effort if you have something that works for you. My reply is mostly so that anyone who comes across this discussion and sees Steve's mention of -A, -B, etc isn't scared off by them. Whilst they're always there for you, you can use the power it gives you but in the form of single function commands that don't require you to think.
---
For anyone wondering, the aliases I mentioned. These can be dropped in your jj config with `jj config edit --user`.