$ git push origin --delete master
Username for 'https://github.com': marcelpetrick
Password for 'https://email@example.com':
! [remote rejected] master (refusing to delete the current branch: refs/heads/master)
error: failed to push some refs to 'https://github.com/marcelpetrick/PiCamGifForTumblr.git'
- create a fake branch and push it
- go to
github > $your_repo > settings > branches > default branchand make the fake branch the current one
- delete master
- push new master
- revert the default branch
The missing counter-part for this post.
- create new smb-user pi: “
$ sudo smbpasswd -a pi“
- create directory: “
$ mkdir freigabeATminipc“
- set rights: “
$ sudo chmod 770 freigabeATminipc/“
- edit config: “
$ sudo nano /etc/samba/smb.conf”
add at end of the file the following and save-quit (CTRL+X; y)
comment = for sharing
path = /home/pi/Desktop/freigabeATminipc
valid users = pi
browseable = yes
read only = no
guest ok = yes
- restart: “
$ sudo service smbd restart“
- check if everything fits: “
When you join a new team, you don’t enforce your view of best tools of trade – instead you adapt to the new environment. Even if that means that you have to switch from your favorite CVS (Git) to something you used last time in 2008 (Subversion) …
I am aware, that the Git-client is fully backward-compatible to SVN and also able to do the most common tasks. But for me it was the branching model, the stashes and also the GUI from SmartGit, which lead me to the idea: why not mix both version-controls in one directory?
- clone the repository via SVN (TortoiseSVN)
$ git init
- add the following stuff to your
1234567891011121314### own #### ignore subversion subdirectories for no conflicts.svn# temporary files and stuff from Qt/target/tmp/*.vcxproj*.vcxproj.filtersmoc_*.cppui_*.h*_moc.cpp*_res.cpp### from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore ##### Ignore Visual Studio temporary files, build results, and files generated by popular Visual Studio add-ons.[..]
- add the following exclusions to your
TortoiseSVN > Settings > General > Subversion > Global ignore-pattern:
- stash, branch, stage as much as you want – use TortoiseSVN for the final commit, which should be published to the team
I use this set-up now for some weeks and it works. Saved me lots of hassles. Because I have not figured out (yet?) how to create local “mile-stones” as safety-backup with SVN.
Edit /boot/config.txt (maybe via “$ sudo nano /boot/config.txt”) and add the following two lines:
framebuffer_width = 1024
framebuffer_height = 768
Other sources suggest also to tinker with the hdmi_mode, but for my Raspberry Pi 3 this was sufficient.
Full official manual for config.txt.
Don’t know how often I did this on several systems and still always(!) have to pick the parameters.
$ sudo apt-fast install samba samba-common smbclient cifs-utils
$ mkdir freigabeATminipc
$ sudo mount -t cifs -o user=guest //MINIPC/freigabe freigabeATminipc/
Check for available shares in the network via “smbtree”.