From c6199c9718e00b882785a4121df4a6d951dec5a4 Mon Sep 17 00:00:00 2001 From: Borislav Date: Thu, 14 Nov 2013 07:44:03 +0200 Subject: [PATCH 1/6] Programming books in Bulgarian --- free-programming-books-bg | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 free-programming-books-bg diff --git a/free-programming-books-bg b/free-programming-books-bg new file mode 100644 index 00000000..b0ec1c77 --- /dev/null +++ b/free-programming-books-bg @@ -0,0 +1,9 @@ +###Index + +* [Въведение в програмирането, алгоритми](#Въведение в програмирането, алгоритми) + +###Въведение в програмирането, алгоритми + +* [Въведение в програмирането със С#](http://www.introprogramming.info/wp-content/uploads/2011/07/Intro-CSharp-Book-1.00.pdf) +* [Програмиране = ++ Алгоритми](http://www.programirane.org/2013/02/free-download-algo-book-nakov-dobrikov/) +* [Въведение в програмирането с Java](http://www.introprogramming.info/intro-java-book/read-online/) From f3b5bfb48f8ceeda4d5e84107f155f58cd56f23b Mon Sep 17 00:00:00 2001 From: Borislav Date: Thu, 14 Nov 2013 07:46:54 +0200 Subject: [PATCH 2/6] Add books in Bulgarian --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index f35953e6..1ec740cc 100644 --- a/README.md +++ b/README.md @@ -29,6 +29,8 @@ The French list was based on Date: Thu, 14 Nov 2013 07:47:45 +0200 Subject: [PATCH 3/6] .md books in Bulgarian --- free-programming-books-bg => free-programming-books-bg.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename free-programming-books-bg => free-programming-books-bg.md (100%) diff --git a/free-programming-books-bg b/free-programming-books-bg.md similarity index 100% rename from free-programming-books-bg rename to free-programming-books-bg.md From 9c6193f87966f05cfaf532ba0f717c26ace0acf9 Mon Sep 17 00:00:00 2001 From: Borislav Date: Sat, 16 Nov 2013 09:36:15 +0200 Subject: [PATCH 4/6] commit 101 --- free-programming-books.git/HEAD | 1 + free-programming-books.git/config | 7 + free-programming-books.git/description | 1 + .../hooks/applypatch-msg.sample | 15 ++ .../hooks/commit-msg.sample | 24 +++ .../hooks/post-update.sample | 8 + .../hooks/pre-applypatch.sample | 14 ++ .../hooks/pre-commit.sample | 49 +++++ .../hooks/pre-push.sample | 53 ++++++ .../hooks/pre-rebase.sample | 169 ++++++++++++++++++ .../hooks/prepare-commit-msg.sample | 36 ++++ .../hooks/update.sample | 128 +++++++++++++ free-programming-books.git/info/exclude | 6 + 13 files changed, 511 insertions(+) create mode 100644 free-programming-books.git/HEAD create mode 100644 free-programming-books.git/config create mode 100644 free-programming-books.git/description create mode 100644 free-programming-books.git/hooks/applypatch-msg.sample create mode 100644 free-programming-books.git/hooks/commit-msg.sample create mode 100644 free-programming-books.git/hooks/post-update.sample create mode 100644 free-programming-books.git/hooks/pre-applypatch.sample create mode 100644 free-programming-books.git/hooks/pre-commit.sample create mode 100644 free-programming-books.git/hooks/pre-push.sample create mode 100644 free-programming-books.git/hooks/pre-rebase.sample create mode 100644 free-programming-books.git/hooks/prepare-commit-msg.sample create mode 100644 free-programming-books.git/hooks/update.sample create mode 100644 free-programming-books.git/info/exclude diff --git a/free-programming-books.git/HEAD b/free-programming-books.git/HEAD new file mode 100644 index 00000000..cb089cd8 --- /dev/null +++ b/free-programming-books.git/HEAD @@ -0,0 +1 @@ +ref: refs/heads/master diff --git a/free-programming-books.git/config b/free-programming-books.git/config new file mode 100644 index 00000000..90e16477 --- /dev/null +++ b/free-programming-books.git/config @@ -0,0 +1,7 @@ +[core] + repositoryformatversion = 0 + filemode = false + bare = true + symlinks = false + ignorecase = true + hideDotFiles = dotGitOnly diff --git a/free-programming-books.git/description b/free-programming-books.git/description new file mode 100644 index 00000000..498b267a --- /dev/null +++ b/free-programming-books.git/description @@ -0,0 +1 @@ +Unnamed repository; edit this file 'description' to name the repository. diff --git a/free-programming-books.git/hooks/applypatch-msg.sample b/free-programming-books.git/hooks/applypatch-msg.sample new file mode 100644 index 00000000..8b2a2fe8 --- /dev/null +++ b/free-programming-books.git/hooks/applypatch-msg.sample @@ -0,0 +1,15 @@ +#!/bin/sh +# +# An example hook script to check the commit log message taken by +# applypatch from an e-mail message. +# +# The hook should exit with non-zero status after issuing an +# appropriate message if it wants to stop the commit. The hook is +# allowed to edit the commit message file. +# +# To enable this hook, rename this file to "applypatch-msg". + +. git-sh-setup +test -x "$GIT_DIR/hooks/commit-msg" && + exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"} +: diff --git a/free-programming-books.git/hooks/commit-msg.sample b/free-programming-books.git/hooks/commit-msg.sample new file mode 100644 index 00000000..b58d1184 --- /dev/null +++ b/free-programming-books.git/hooks/commit-msg.sample @@ -0,0 +1,24 @@ +#!/bin/sh +# +# An example hook script to check the commit log message. +# Called by "git commit" with one argument, the name of the file +# that has the commit message. The hook should exit with non-zero +# status after issuing an appropriate message if it wants to stop the +# commit. The hook is allowed to edit the commit message file. +# +# To enable this hook, rename this file to "commit-msg". + +# Uncomment the below to add a Signed-off-by line to the message. +# Doing this in a hook is a bad idea in general, but the prepare-commit-msg +# hook is more suited to it. +# +# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p') +# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1" + +# This example catches duplicate Signed-off-by lines. + +test "" = "$(grep '^Signed-off-by: ' "$1" | + sort | uniq -c | sed -e '/^[ ]*1[ ]/d')" || { + echo >&2 Duplicate Signed-off-by lines. + exit 1 +} diff --git a/free-programming-books.git/hooks/post-update.sample b/free-programming-books.git/hooks/post-update.sample new file mode 100644 index 00000000..ec17ec19 --- /dev/null +++ b/free-programming-books.git/hooks/post-update.sample @@ -0,0 +1,8 @@ +#!/bin/sh +# +# An example hook script to prepare a packed repository for use over +# dumb transports. +# +# To enable this hook, rename this file to "post-update". + +exec git update-server-info diff --git a/free-programming-books.git/hooks/pre-applypatch.sample b/free-programming-books.git/hooks/pre-applypatch.sample new file mode 100644 index 00000000..b1f187c2 --- /dev/null +++ b/free-programming-books.git/hooks/pre-applypatch.sample @@ -0,0 +1,14 @@ +#!/bin/sh +# +# An example hook script to verify what is about to be committed +# by applypatch from an e-mail message. +# +# The hook should exit with non-zero status after issuing an +# appropriate message if it wants to stop the commit. +# +# To enable this hook, rename this file to "pre-applypatch". + +. git-sh-setup +test -x "$GIT_DIR/hooks/pre-commit" && + exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"} +: diff --git a/free-programming-books.git/hooks/pre-commit.sample b/free-programming-books.git/hooks/pre-commit.sample new file mode 100644 index 00000000..586e3bf9 --- /dev/null +++ b/free-programming-books.git/hooks/pre-commit.sample @@ -0,0 +1,49 @@ +#!/bin/sh +# +# An example hook script to verify what is about to be committed. +# Called by "git commit" with no arguments. The hook should +# exit with non-zero status after issuing an appropriate message if +# it wants to stop the commit. +# +# To enable this hook, rename this file to "pre-commit". + +if git rev-parse --verify HEAD >/dev/null 2>&1 +then + against=HEAD +else + # Initial commit: diff against an empty tree object + against=4b825dc642cb6eb9a060e54bf8d69288fbee4904 +fi + +# If you want to allow non-ASCII filenames set this variable to true. +allownonascii=$(git config hooks.allownonascii) + +# Redirect output to stderr. +exec 1>&2 + +# Cross platform projects tend to avoid non-ASCII filenames; prevent +# them from being added to the repository. We exploit the fact that the +# printable range starts at the space character and ends with tilde. +if [ "$allownonascii" != "true" ] && + # Note that the use of brackets around a tr range is ok here, (it's + # even required, for portability to Solaris 10's /usr/bin/tr), since + # the square bracket bytes happen to fall in the designated range. + test $(git diff --cached --name-only --diff-filter=A -z $against | + LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0 +then + cat <<\EOF +Error: Attempt to add a non-ASCII file name. + +This can cause problems if you want to work with people on other platforms. + +To be portable it is advisable to rename the file. + +If you know what you are doing you can disable this check using: + + git config hooks.allownonascii true +EOF + exit 1 +fi + +# If there are whitespace errors, print the offending file names and fail. +exec git diff-index --check --cached $against -- diff --git a/free-programming-books.git/hooks/pre-push.sample b/free-programming-books.git/hooks/pre-push.sample new file mode 100644 index 00000000..15ab6d8e --- /dev/null +++ b/free-programming-books.git/hooks/pre-push.sample @@ -0,0 +1,53 @@ +#!/bin/sh + +# An example hook script to verify what is about to be pushed. Called by "git +# push" after it has checked the remote status, but before anything has been +# pushed. If this script exits with a non-zero status nothing will be pushed. +# +# This hook is called with the following parameters: +# +# $1 -- Name of the remote to which the push is being done +# $2 -- URL to which the push is being done +# +# If pushing without using a named remote those arguments will be equal. +# +# Information about the commits which are being pushed is supplied as lines to +# the standard input in the form: +# +# +# +# This sample shows how to prevent push of commits where the log message starts +# with "WIP" (work in progress). + +remote="$1" +url="$2" + +z40=0000000000000000000000000000000000000000 + +IFS=' ' +while read local_ref local_sha remote_ref remote_sha +do + if [ "$local_sha" = $z40 ] + then + # Handle delete + else + if [ "$remote_sha" = $z40 ] + then + # New branch, examine all commits + range="$local_sha" + else + # Update to existing branch, examine new commits + range="$remote_sha..$local_sha" + fi + + # Check for WIP commit + commit=`git rev-list -n 1 --grep '^WIP' "$range"` + if [ -n "$commit" ] + then + echo "Found WIP commit in $local_ref, not pushing" + exit 1 + fi + fi +done + +exit 0 diff --git a/free-programming-books.git/hooks/pre-rebase.sample b/free-programming-books.git/hooks/pre-rebase.sample new file mode 100644 index 00000000..9773ed4c --- /dev/null +++ b/free-programming-books.git/hooks/pre-rebase.sample @@ -0,0 +1,169 @@ +#!/bin/sh +# +# Copyright (c) 2006, 2008 Junio C Hamano +# +# The "pre-rebase" hook is run just before "git rebase" starts doing +# its job, and can prevent the command from running by exiting with +# non-zero status. +# +# The hook is called with the following parameters: +# +# $1 -- the upstream the series was forked from. +# $2 -- the branch being rebased (or empty when rebasing the current branch). +# +# This sample shows how to prevent topic branches that are already +# merged to 'next' branch from getting rebased, because allowing it +# would result in rebasing already published history. + +publish=next +basebranch="$1" +if test "$#" = 2 +then + topic="refs/heads/$2" +else + topic=`git symbolic-ref HEAD` || + exit 0 ;# we do not interrupt rebasing detached HEAD +fi + +case "$topic" in +refs/heads/??/*) + ;; +*) + exit 0 ;# we do not interrupt others. + ;; +esac + +# Now we are dealing with a topic branch being rebased +# on top of master. Is it OK to rebase it? + +# Does the topic really exist? +git show-ref -q "$topic" || { + echo >&2 "No such branch $topic" + exit 1 +} + +# Is topic fully merged to master? +not_in_master=`git rev-list --pretty=oneline ^master "$topic"` +if test -z "$not_in_master" +then + echo >&2 "$topic is fully merged to master; better remove it." + exit 1 ;# we could allow it, but there is no point. +fi + +# Is topic ever merged to next? If so you should not be rebasing it. +only_next_1=`git rev-list ^master "^$topic" ${publish} | sort` +only_next_2=`git rev-list ^master ${publish} | sort` +if test "$only_next_1" = "$only_next_2" +then + not_in_topic=`git rev-list "^$topic" master` + if test -z "$not_in_topic" + then + echo >&2 "$topic is already up-to-date with master" + exit 1 ;# we could allow it, but there is no point. + else + exit 0 + fi +else + not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"` + /usr/bin/perl -e ' + my $topic = $ARGV[0]; + my $msg = "* $topic has commits already merged to public branch:\n"; + my (%not_in_next) = map { + /^([0-9a-f]+) /; + ($1 => 1); + } split(/\n/, $ARGV[1]); + for my $elem (map { + /^([0-9a-f]+) (.*)$/; + [$1 => $2]; + } split(/\n/, $ARGV[2])) { + if (!exists $not_in_next{$elem->[0]}) { + if ($msg) { + print STDERR $msg; + undef $msg; + } + print STDERR " $elem->[1]\n"; + } + } + ' "$topic" "$not_in_next" "$not_in_master" + exit 1 +fi + +exit 0 + +################################################################ + +This sample hook safeguards topic branches that have been +published from being rewound. + +The workflow assumed here is: + + * Once a topic branch forks from "master", "master" is never + merged into it again (either directly or indirectly). + + * Once a topic branch is fully cooked and merged into "master", + it is deleted. If you need to build on top of it to correct + earlier mistakes, a new topic branch is created by forking at + the tip of the "master". This is not strictly necessary, but + it makes it easier to keep your history simple. + + * Whenever you need to test or publish your changes to topic + branches, merge them into "next" branch. + +The script, being an example, hardcodes the publish branch name +to be "next", but it is trivial to make it configurable via +$GIT_DIR/config mechanism. + +With this workflow, you would want to know: + +(1) ... if a topic branch has ever been merged to "next". Young + topic branches can have stupid mistakes you would rather + clean up before publishing, and things that have not been + merged into other branches can be easily rebased without + affecting other people. But once it is published, you would + not want to rewind it. + +(2) ... if a topic branch has been fully merged to "master". + Then you can delete it. More importantly, you should not + build on top of it -- other people may already want to + change things related to the topic as patches against your + "master", so if you need further changes, it is better to + fork the topic (perhaps with the same name) afresh from the + tip of "master". + +Let's look at this example: + + o---o---o---o---o---o---o---o---o---o "next" + / / / / + / a---a---b A / / + / / / / + / / c---c---c---c B / + / / / \ / + / / / b---b C \ / + / / / / \ / + ---o---o---o---o---o---o---o---o---o---o---o "master" + + +A, B and C are topic branches. + + * A has one fix since it was merged up to "next". + + * B has finished. It has been fully merged up to "master" and "next", + and is ready to be deleted. + + * C has not merged to "next" at all. + +We would want to allow C to be rebased, refuse A, and encourage +B to be deleted. + +To compute (1): + + git rev-list ^master ^topic next + git rev-list ^master next + + if these match, topic has not merged in next at all. + +To compute (2): + + git rev-list master..topic + + if this is empty, it is fully merged to "master". diff --git a/free-programming-books.git/hooks/prepare-commit-msg.sample b/free-programming-books.git/hooks/prepare-commit-msg.sample new file mode 100644 index 00000000..f093a02e --- /dev/null +++ b/free-programming-books.git/hooks/prepare-commit-msg.sample @@ -0,0 +1,36 @@ +#!/bin/sh +# +# An example hook script to prepare the commit log message. +# Called by "git commit" with the name of the file that has the +# commit message, followed by the description of the commit +# message's source. The hook's purpose is to edit the commit +# message file. If the hook fails with a non-zero status, +# the commit is aborted. +# +# To enable this hook, rename this file to "prepare-commit-msg". + +# This hook includes three examples. The first comments out the +# "Conflicts:" part of a merge commit. +# +# The second includes the output of "git diff --name-status -r" +# into the message, just before the "git status" output. It is +# commented because it doesn't cope with --amend or with squashed +# commits. +# +# The third example adds a Signed-off-by line to the message, that can +# still be edited. This is rarely a good idea. + +case "$2,$3" in + merge,) + /usr/bin/perl -i.bak -ne 's/^/# /, s/^# #/#/ if /^Conflicts/ .. /#/; print' "$1" ;; + +# ,|template,) +# /usr/bin/perl -i.bak -pe ' +# print "\n" . `git diff --cached --name-status -r` +# if /^#/ && $first++ == 0' "$1" ;; + + *) ;; +esac + +# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p') +# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1" diff --git a/free-programming-books.git/hooks/update.sample b/free-programming-books.git/hooks/update.sample new file mode 100644 index 00000000..d8475837 --- /dev/null +++ b/free-programming-books.git/hooks/update.sample @@ -0,0 +1,128 @@ +#!/bin/sh +# +# An example hook script to blocks unannotated tags from entering. +# Called by "git receive-pack" with arguments: refname sha1-old sha1-new +# +# To enable this hook, rename this file to "update". +# +# Config +# ------ +# hooks.allowunannotated +# This boolean sets whether unannotated tags will be allowed into the +# repository. By default they won't be. +# hooks.allowdeletetag +# This boolean sets whether deleting tags will be allowed in the +# repository. By default they won't be. +# hooks.allowmodifytag +# This boolean sets whether a tag may be modified after creation. By default +# it won't be. +# hooks.allowdeletebranch +# This boolean sets whether deleting branches will be allowed in the +# repository. By default they won't be. +# hooks.denycreatebranch +# This boolean sets whether remotely creating branches will be denied +# in the repository. By default this is allowed. +# + +# --- Command line +refname="$1" +oldrev="$2" +newrev="$3" + +# --- Safety check +if [ -z "$GIT_DIR" ]; then + echo "Don't run this script from the command line." >&2 + echo " (if you want, you could supply GIT_DIR then run" >&2 + echo " $0 )" >&2 + exit 1 +fi + +if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then + echo "usage: $0 " >&2 + exit 1 +fi + +# --- Config +allowunannotated=$(git config --bool hooks.allowunannotated) +allowdeletebranch=$(git config --bool hooks.allowdeletebranch) +denycreatebranch=$(git config --bool hooks.denycreatebranch) +allowdeletetag=$(git config --bool hooks.allowdeletetag) +allowmodifytag=$(git config --bool hooks.allowmodifytag) + +# check for no description +projectdesc=$(sed -e '1q' "$GIT_DIR/description") +case "$projectdesc" in +"Unnamed repository"* | "") + echo "*** Project description file hasn't been set" >&2 + exit 1 + ;; +esac + +# --- Check types +# if $newrev is 0000...0000, it's a commit to delete a ref. +zero="0000000000000000000000000000000000000000" +if [ "$newrev" = "$zero" ]; then + newrev_type=delete +else + newrev_type=$(git cat-file -t $newrev) +fi + +case "$refname","$newrev_type" in + refs/tags/*,commit) + # un-annotated tag + short_refname=${refname##refs/tags/} + if [ "$allowunannotated" != "true" ]; then + echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2 + echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2 + exit 1 + fi + ;; + refs/tags/*,delete) + # delete tag + if [ "$allowdeletetag" != "true" ]; then + echo "*** Deleting a tag is not allowed in this repository" >&2 + exit 1 + fi + ;; + refs/tags/*,tag) + # annotated tag + if [ "$allowmodifytag" != "true" ] && git rev-parse $refname > /dev/null 2>&1 + then + echo "*** Tag '$refname' already exists." >&2 + echo "*** Modifying a tag is not allowed in this repository." >&2 + exit 1 + fi + ;; + refs/heads/*,commit) + # branch + if [ "$oldrev" = "$zero" -a "$denycreatebranch" = "true" ]; then + echo "*** Creating a branch is not allowed in this repository" >&2 + exit 1 + fi + ;; + refs/heads/*,delete) + # delete branch + if [ "$allowdeletebranch" != "true" ]; then + echo "*** Deleting a branch is not allowed in this repository" >&2 + exit 1 + fi + ;; + refs/remotes/*,commit) + # tracking branch + ;; + refs/remotes/*,delete) + # delete tracking branch + if [ "$allowdeletebranch" != "true" ]; then + echo "*** Deleting a tracking branch is not allowed in this repository" >&2 + exit 1 + fi + ;; + *) + # Anything else (is there anything else?) + echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2 + exit 1 + ;; +esac + +# --- Finished +exit 0 diff --git a/free-programming-books.git/info/exclude b/free-programming-books.git/info/exclude new file mode 100644 index 00000000..a5196d1b --- /dev/null +++ b/free-programming-books.git/info/exclude @@ -0,0 +1,6 @@ +# git ls-files --others --exclude-from=.git/info/exclude +# Lines that start with '#' are comments. +# For a project mostly in C, the following would be a good set of +# exclude patterns (uncomment them if you want to use them): +# *.[oa] +# *~ From b1b3074c2ffa9c42aedf20260838db2d1139c0e7 Mon Sep 17 00:00:00 2001 From: Borislav Date: Sat, 16 Nov 2013 09:46:29 +0200 Subject: [PATCH 5/6] commit 101 --- free-programming-books | 1 + free-programming-books-bg | 0 free-programming-books-bg.md | 6 +++--- 3 files changed, 4 insertions(+), 3 deletions(-) create mode 160000 free-programming-books create mode 100644 free-programming-books-bg diff --git a/free-programming-books b/free-programming-books new file mode 160000 index 00000000..32d4979f --- /dev/null +++ b/free-programming-books @@ -0,0 +1 @@ +Subproject commit 32d4979f686ce6f81a8e5ef6722680013bdddb10 diff --git a/free-programming-books-bg b/free-programming-books-bg new file mode 100644 index 00000000..e69de29b diff --git a/free-programming-books-bg.md b/free-programming-books-bg.md index b0ec1c77..1a78a404 100644 --- a/free-programming-books-bg.md +++ b/free-programming-books-bg.md @@ -4,6 +4,6 @@ ###Въведение в програмирането, алгоритми -* [Въведение в програмирането със С#](http://www.introprogramming.info/wp-content/uploads/2011/07/Intro-CSharp-Book-1.00.pdf) -* [Програмиране = ++ Алгоритми](http://www.programirane.org/2013/02/free-download-algo-book-nakov-dobrikov/) -* [Въведение в програмирането с Java](http://www.introprogramming.info/intro-java-book/read-online/) +* [Въведение в програмирането със С#](http://www.introprogramming.info/wp-content/uploads/2011/07/Intro-CSharp-Book-1.00.pdf) - С.Наков +* [Програмиране = ++ Алгоритми](http://www.programirane.org/2013/02/free-download-algo-book-nakov-dobrikov/) - Преслав Наков и Панайот Добриков +* [Въведение в програмирането с Java](http://www.introprogramming.info/intro-java-book/read-online/) - С.Наков From 4a420987bbfa361396401bb4454924f317fd2975 Mon Sep 17 00:00:00 2001 From: Borislav Date: Sat, 16 Nov 2013 10:04:04 +0200 Subject: [PATCH 6/6] empty file --- free-programming-books-bg | 0 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 free-programming-books-bg diff --git a/free-programming-books-bg b/free-programming-books-bg deleted file mode 100644 index e69de29b..00000000