| # | |
| # mkcd command | |
| # This is an improvised version of the mkcd command at http://superuser.com/questions/152794/is-there-a-shortcut-to-mkdir-foo-and-immediately-cd-into-it | |
| # This function has to be added to the ~/.bashrc file | |
| # After that you can run command like: mkdir abc, mkdir -p one/two/three | |
| # | |
| function mkcd { | |
| last=$(eval "echo \$$#") | |
| if [ ! -n "$last" ]; then | |
| echo "Enter a directory name" |
Setup GitHub Pages "gh-pages" branch as a subfolder within the "master" project on your local checkout.
If you plan on switching between different branches (e.g. git checkout master-experiment
then revert back with git checkout master) you will loose your child folder from this tutorial (because it's in your
.gitignore and is not part of your master branch).
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: |
| import std.stdio, std.file, std.path, std.range, std.string, std.algorithm ; | |
| string[] filterList = ["./test_runner.d", "./Makefile.in", "./gcc/config.d.in", "./gcc/libbacktrace.d.in", "./phobos-ver-syms.in", | |
| "./Makefile.am", "./LICENSE_1_0.txt", "./README.txt", "./rt/dylib_fixes.c"]; | |
| struct Files | |
| { | |
| string[] baseList, gcList, gcStubList; | |
| string[][string] sysList; | |
| } |
[ Update 2020-05-31: I won't be maintaining this page or responding to comments anymore (except for perhaps a few exceptional occasions). ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
(draft; work in progress)
See also:
The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.
It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.
Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.
This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that
