Re: [msysGit] Re: [PATCH] t/lib-httpd: switch SANITY check for NOT_ROOT

Hm, being one day offline and there are lots of ideas and new patches, I like that. I run these test under msys and cygwin on latest pu (a3dc223ff234481356c): ./t0001-init.sh ./t0004-unwritable.sh ./t0061-run-command.sh ./t0070-fundamental.sh ./t1004-read-tree-m-u-wf.sh ./t1300-repo-config.sh

[PATCH] git-p4: support exclude in 'git p4 sync'

The git-p4 'clone' subcommand has long had the option to specify parts of the repo to be excluded, on the command line. But this has not been present in 'sync', which makes it less than useful: as soon as you do a sync, the excluded parts start being repopulated as those directories are changed.

[PATCH] git-p4: support excluding paths on sync

The clone subcommand has long had support for excluding subdirectories, but sync has not. This is a nuisance, since as soon as you do a sync, any changed files that were initially excluded start showing up. Move the exclude command-line option into the parent class; the actual behavior was

[PATCH] .clang-format: introduce the use of clang-format

Instead of manually eyeballing style in reviews, just ask all contributors to run their patches through [git-]clang-format. Signed-off-by: Ramkumar Ramachandra artag...@gmail.com --- The idea is to introduce the community to this new toy I found called clang-format. Whether or not it's actually

Re: [PATCH] Documentation/git-branch.txt: add short option to git branch synopsis

s/short/long/ Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to

.gitattributes on branch behaves unexpected. Should it be more stateless?

Hi, I am asking myself if git and .gitattributes should be more stateless? i.e. whatever you have done before is irrelevant, when you reach status XYZ with your git repo, it is EXACTLY and BINARY the same all the time and everywhere. It took some time for me to figure out, that depending on HOW

zsh completion for `git push origin --delete`

The man for `--delete` says only refs on the remote repo are affected. Then, the auto-completion in zsh shall not return local refs. ``` $ git branch -a master * tmp remotes/origin/master remotes/origin/tmp $ git push origin --delete tab FETCH_HEAD HEAD master

Re: [PATCH] branch: add support for --dry-run option

From: Alexander Kuleshov kuleshovm...@gmail.com This patch adds support -d/--dry-run option for branch(es) deletion. If -d/--dry-run option passed to git branch -d branch..., branch(es) surely s|-d/--dry-run|-n/--dry-run| -n is the short version of --dryrun. -d is already in use. will not be

Re: .gitattributes on branch behaves unexpected. Should it be more stateless?

Hi, I am asking myself if git and .gitattributes should be more stateless? i.e. whatever you have done before is irrelevant, when you reach status XYZ with your git repo, it is EXACTLY and BINARY the same all the time and everywhere. It took some time for me to figure out, that depending on

[PATCH v2] Documentation/git-branch.txt: add long options to git branch synopsis

Signed-off-by: Alexander Kuleshov kuleshovm...@gmail.com --- Documentation/git-branch.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt index 311b336..722f865 100644 --- a/Documentation/git-branch.txt +++

[PATCH v2] branch: add support for --dry-run option

This patch adds support -n/--dry-run option for branch(es) deletion. If -n/--dry-run option passed to git branch -d branch..., branch(es) will not be removed, instead just print list of branches that are to be removed. For example: $ git branch a b c * master $ git

Re: [PATCH] l10n: de.po: translate 13 new messages

Am 16. Januar 2015 um 23:31 schrieb phillip phillip.sze...@gmail.com: looks good! Thanks for review! -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html