johnkeeping

4 ms·

1.
by johnkeeping 11y ago
The bug was in the RK808 PMIC, which may or may not be used on an RK3288 based system. It looks like the RK3288-based ChromeOS devices do use it though.
2.
by johnkeeping 11y ago
How does this compare to git-worktree (added to core Git in 2.5)?
3.
by johnkeeping 11y ago
That's what the `--autostash` is for. It also has the advantage that the stash will be restored at the end of the rebase even if it hits problems and needs to be continued or aborted.
4.
by johnkeeping 11y ago
`local` is a bash-ism so it's best avoided in this context, and the command is running in its own shell anyway so the variables can't pollute anything else. The other comments are 100% correct.
5.
by johnkeeping 11y ago
Or simply: git add ... git commit --fixup $SHA git rebase -i --autosquash --autostash $SHA~
6.
Git Rev News: Edition 1(git.github.io)
8 points by johnkeeping 12y ago|4 comments
7.
by johnkeeping 12y ago
Note that this is only the Zigbee Light Link master key. A lot of devices use the Zigbee Home Automation specification which has a different well known master key (in that case it's in the standard which is freely available). The ZLL
8.
by johnkeeping 12y ago
I always use "--no-ff" when merging topic branches to master. The advantage is that you can keep individual commits on the topic branch readable and still get an overview of the changes between two releases with "git log --f
9.
by johnkeeping 12y ago
The ImperialViolet post linked above gives a different URL for the blog post which does work: http://ccsinjection.lepidum.co.jp/blog/2014-06-05/CCS-Inject...
10.
by johnkeeping 12y ago
There's also sparse[0]'s address space annotation, which Linux uses for annotating data from userspace. [0] https://git.kernel.org/cgit/devel/sparse/sparse.git/