- 03 Dec, 2020 1 commit
-
-
Stimim Chen authored
check_output() in get_tagname_or_hash() returns bytes instead of str in python3. Decode the return value to utf-8, this works in both python2 and python3. Co-authored-by: Stimim Chen <stimim@google.com>
-
- 13 Oct, 2020 1 commit
-
-
Gonçalo Queirós authored
-
- 21 Dec, 2019 1 commit
-
-
lieryan authored
Fix the finicky parsing logic and just ask git the necessary information directly.
-
- 19 Nov, 2019 1 commit
-
-
Jacob Tomaw authored
Use add-zsh-hook to add functions to hooks. That way they won't be added again when doing `source ~/.zshrc` multiple times. Co-authored-by: Marc Cornellà <marc.cornella@live.com>
-
- 10 Apr, 2019 1 commit
-
-
Marc Cornellà authored
The previous version modified the whole environment leading to problems (see #7757). This version *adds* LANG=C to the current env, without overriding it completely. Fixes #7757.
-
- 09 Apr, 2019 1 commit
-
-
Jayden Thrasher authored
-
- 07 Apr, 2019 1 commit
-
-
sheveko authored
As described in #6086 there will be an error when one set another language than English.
-
- 07 Aug, 2018 1 commit
-
-
Janosch Schwalm authored
* use https everywhere * use https links on the files that are left Also, removed some broken links and updated redirections.
-
- 29 Jul, 2018 1 commit
-
-
Thanh Ha authored
When a commit has multiple tags associated to it, the git-prompt will throw the following error: git_super_status:[:4: integer expression expected: v0.21.x\ntags/v0.21.5, git_super_status:[:7: integer expression expected: origin/v0.21.x, git_super_status:[:11: integer expression expected: origin/v0.21.x, git_super_status:[:14: integer expression expected: v0.21.x git_super_status:[:23: integer expression expected: v0.21.x This is due to the prompt expecting the tag field to be a single word with no spaces in between but if there are multiple tags the python script returns a string with ', ' space separated list of tags. This throws off the parser. The solution is to ensure that the python script returns a space-less string ensuring the git-prompt parser to properly parse the data. Signed-off-by: Thanh Ha <zxiiro@linux.com>
-
- 30 Apr, 2018 1 commit
-
-
Oliver Baumann authored
Inside a fresh git repo, i.e. immediately after a `git init`, usually no commit template exists yet. In this case, git renders a different status message than "Initial commit on". We should consider this message when attempting to parse out the branch name. Fixes #6301
-
- 17 Aug, 2015 1 commit
-
-
Kentaro Wada authored
-
- 16 Aug, 2015 8 commits
-
-
Marc Cornellà authored
-
Kentaro Wada authored
-
Marc Cornellà authored
-
Kentaro Wada authored
This commit uses the `git status --porcelain -b` format to gather the number of ahead and behind commits related to the remote branch.
-
Marc Cornellà authored
-
Marc Cornellà authored
-
Marc Cornellà authored
This version uses `git status --porcelain` instead of making multiple calls to `git status`.
-
Marc Cornellà authored
-
- 10 Feb, 2015 1 commit
-
-
Marc Cornellà authored
-
- 16 Jul, 2014 1 commit
-
- 04 Jun, 2014 1 commit
-
-
ncanceill authored
as suggested in #2382
-
- 18 Apr, 2014 1 commit
-
-
Paweł Tomak authored
In Python3 without universal_newlines set to True output from Popen was byte-encoded.
-
- 22 Feb, 2014 2 commits
-
-
Chris Jones authored
-
Chris Jones authored
-
- 28 Apr, 2011 1 commit
-
-
Justin Riley authored
-