Archiving the whole directory is also an idea, but why not use the integrated functionality?
More hints: https://stackoverflow.com/a/5578292/1694302
export to a single file (bunlde):
git bundle create ../SAP_autoIt_bundle --all
git clone SAP_autoIt_bundle myClonedFolder
As always: some projects need a first (working) implementation and then over time you can improve them.
During lunch I was talking with a colleague about this tool. Then the idea to just use those actually changed files from the current implementation (means: the current branch in Git) shall be used as input. Et voila: consider it done!
Also added some fine-tuning to the call-parameter of the script itself, so it can be run as well with some custom string beside “todoM” (which is my marker).
Cleaning an implementation of properly tagged lines takes now a second – not minutes (like before!
Enjoy and have fun 🙂
Code can be found as always at https://github.com/marcelpetrick/cleanMyCode/blob/master/remove_todoM.sh
$ 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
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.
~ Linus Torvalds
I’ve given Visual Studio Code for Linux as prebuilt rpm-package a try. I don’t know what I expected ten minutes ago, but I am definitely under-whelmed! Another editor with syntax-highlighting, code-completion, integrated git-support and the ability to add “extensions” for all kinds of stuff. But: do I miss the trick or how do I start build binaries? (edith: possible via some “we need another build-configuration-system..”-JSON).
OK, it was fun to test, but now back to my favorite IDE* 😉 gedit & gcc on the terminal can do the same, so I don’t see any reason to use VS Code. Maybe for Go or one of the other languages, but not C++.
Just to close the topic: I finished what I planned for the forked QtScrobbler-project. I changed the workflow, so that if you did not provide correct credentials for your favourite submission-site (last.fm, libre.fm ..), then the progress-dialog will be closed and you will see immediately the error in the ui (not just log). Because before the user could wait until the cows come home – and I found this really annoying, especially when I set up QtScrobbler on a new system, mistyped or forgot to set the credentials at all.
Besides: also cleaned the code a little bit with the help of cppcheck 😉
The repository: https://github.com/marcelpetrick/QTScrobbler
All in all it was a nice experience: set up GitHub, clone the repository, work into a medium large project, try to fix an error without breaking the remaining functionality ..
I do not fully agree to the original code of conduct for style and includes. But as long as it is comprehensive ..
I want to fix several smaller, but annoying issues with QtScrobbler. Originally hosted on sourceforge, but development was discontinued in 2013. I mean: it worked. I used it for years with my upgraded SANSA clips.
So I forked the project to github, upgraded the whole project to the current Qt-version (5.5) and fixed immediately some ‘klein-klein’. But now I am too tired …
I fixed a small glitch, which was included in the first releases: input-filenames with spaces were not treated correctly therefore no result was created. Fixed by some string-replacement and setting the IFS-variable which dictates that bash should treat spaces not as separators.
For the next release some filename-embedding into the thumbnail is planned. But this has to happen after the negfix8-conversion else it would alter the conversion itself ..
Download this: version_0.3
Small hint: git offers a really nice exporting-function which will just include the current state of the given branch:
git archive master --output="version_0.3.zip"
To appraise the tenth anniversary of Git, I want to introduce another tool for measuring the performance for whole repositories: gitstats.
I ran it over quite huge repos and small ones, precompiled for Linux and self-built for OSX and its capabilities and output are really nice. You can even truncate certain timeframes from the visualised data, etc. Output is HTML.
For a small example I ran it over one upcoming project – since I am the lone contributor, some graphs are really lonely.
External link <- can be down.