Unfortunately, you can’t pipe schematics to gschem’s stdin (that I know of). Even if you could, we want to compare two schematics, so how would you pipe two files to stdin? It all seemed pretty tough to me until I found a post on stack overflow showing exactly how to handle it… Using process substitution, it becomes an easy problem:
#!/bin/bash
# See the last committed and current versions of a file
gschem <(git show HEAD:SOME_FILE) SOME_FILE
# See any two files in history
gschem <(git show OBJECT) <(git show OBJECT)
When committing with git, you have to include a message. The standard one-liners can be useful to you or anybody else trying to make heads or tails of a particular commit. But what if you need more room than 80 characters? You can do that.
Here’s a handy little script for your .git/hooks folder…
I’ve been getting into git and along with that, I’ve been trying to be more standards minded. Part of that entails including a LICENSE and README file. The LICENSE file is as ease as: