The Z-Stick does bi-directional communication over a UART. The connection speed is 115200, '8N1'. There are "requests" and "responses". The client software can make requests to the Z-Stick, and it will send responses. But it seems the Z-Stick can make requests of the client software too. I have yet to figure out the requests the Z-Stick sends to the client software.
|# Working with Altera Quartus II (Q2) and do proper versioning is not that easy|
|# but if you follow some rules it can be accomplished. :)|
|# This file should be placed into the main directory where the .qpf file is|
|# found. Generally Q2 throws all entities and so on in the main directory, but|
|# you can place all stuff also in separate folders. This approach is followed|
|# here. So when you create a new design create one or more folders where your|
|# entities will be located and put a .gitignore in there that overrides the|
|# ignores of this file, e.g. one single rule stating "!*" which allows now all|
|# type of files. When you add a MegaFunction or another entity to your design,|
|# simply add it to one of your private folders and Q2 will be happy and manage|
Creates a .bacpac file from live database.
"C:\Program Files (x86)\Microsoft SQL Server\140\DAC\bin\SqlPackage.exe" /a:Export /scs:"Data Source=SERVER;Initial Catalog=db_name;Integrated Security=False;Persist Security Info=False;User ID=db_user;Password=db_password" /tf:"D:\backup\database_backup.bacpac"
Import from .bacpac file to database.
|So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!|
|Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.|
|* Off the top of my head *|
|1. Fork their repo on Github|
|2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it|
|git remote add my-fork git@github...my-fork.git|