Le 04.01.2016 23:16, Luke Diamand a écrit :
On 4 January 2016 at 10:52, Romain Picard
wrote:
After changing the type of a file in the git repository, it is not
possible to
"git p4 publish" the commit to perforce. This is due to the fact that
the git
"T" status is not handled in git-p4.py. This
On 4 January 2016 at 10:52, Romain Picard wrote:
> After changing the type of a file in the git repository, it is not possible to
> "git p4 publish" the commit to perforce. This is due to the fact that the git
> "T" status is not handled in git-p4.py. This can typically occur when
> replacing
> a
Romain Picard writes:
> diff --git a/t/t9827-git-p4-change-filetype.sh
> b/t/t9827-git-p4-change-filetype.sh
> new file mode 100755
> index 000..b0a9f62
> --- /dev/null
> +++ b/t/t9827-git-p4-change-filetype.sh
> @@ -0,0 +1,69 @@
> +#!/bin/sh
> +#
> +# Copyright (c) 2016 Romain Picard
> +#
>
After changing the type of a file in the git repository, it is not possible to
"git p4 publish" the commit to perforce. This is due to the fact that the git
"T" status is not handled in git-p4.py. This can typically occur when replacing
an existing file with a symbolic link.
The "T" modifier is no
4 matches
Mail list logo