At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.
git commit --amendThis will open your $EDITOR and let you change the message. Continue with your usual git push origin master.
| ### Keybase proof | |
| I hereby claim: | |
| * I am dougsland on github. | |
| * I am dougsland (https://keybase.io/dougsland) on keybase. | |
| * I have a public key whose fingerprint is A13D 1ABC 798F 0660 4D28 C77B AD27 5D27 3278 1901 | |
| To claim this, I am signing this object: |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
Typing vagrant from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)
NetworkManager supports WiFi powersaving but the function is rather undocumented.
From the source code: wifi.powersave can have the following value:
| # Note: not sure who wrote this, but thank you | |
| # Note: ~/.ssh/environment should not be used, as it | |
| # already has a different purpose in SSH. | |
| env=~/.ssh/agent.env | |
| # Note: Don't bother checking SSH_AGENT_PID. It's not used | |
| # by SSH itself, and it might even be incorrect | |
| # (for example, when using agent-forwarding over SSH). |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| # busctl introspect org.eclipse.bluechi /org/eclipse/bluechi | |
| NAME TYPE SIGNATURE RESULT/VALUE FLAGS | |
| org.eclipse.bluechi.Manager interface - - - | |
| .CreateMonitor method - o - | |
| .DisableMetrics method - - - | |
| .EnableMetrics method - - - | |
| .GetNode method s o - | |
| .ListNodes method - a(sos) - | |
| .ListUnits method - a(sssssssouso) - | |
| .Ping method s s - |
| # Rust | |
| Rust developers can take advance of **dbus-codegen-rust** to generate a Rust module | |
| and use,tag,release in any pace it's appropriate to their project. | |
| ## Generating bluechi module | |
| Make sure a BlueChi node is running and execute the below commands. | |
| ``` bash | |
| # dnf install rust cargo |
| dnf install g++ dbus-devel -y | |
| g++ -o list_nodes list_nodes.cpp -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include/ -ldbus-1 | |
| #include <dbus/dbus.h> | |
| #include <iostream> | |
| void handle_structure(DBusMessageIter *structIter) { | |
| int typeInStruct; | |
| while ((typeInStruct = dbus_message_iter_get_arg_type( |