Thx jeff, i will try it tomorrow.
> Am 24.07.2017 um 22:32 schrieb Jeff King :
>
> On Mon, Jul 24, 2017 at 10:26:22PM +0200, tonka3...@gmail.com wrote:
>
>>> I'm not sure exactly what you're trying to accomplish. If you're unhappy
>>> with the file as utf-16, then you should
On Mon, Jul 24, 2017 at 10:26:22PM +0200, tonka3...@gmail.com wrote:
> > I'm not sure exactly what you're trying to accomplish. If you're unhappy
> > with the file as utf-16, then you should probably convert to utf-8 as a
> > single commit (since the diff will otherwise be unreadable) and then
>
On Mon, Jul 24, 2017 at 09:02:12PM +0200, tonka3...@gmail.com wrote:
> There is no .gitattributes file in the repo. I think that the git
> heuristic will also detect utf-16 files as binary (in windows), so i
> think that is the reason why my file is binary (i have to check that
> tomorrow).
Hey Jeff,
Thx for your answer.
There is no .gitattributes file in the repo. I think that the git heuristic
will also detect utf-16 files as binary (in windows), so i think that is the
reason why my file is binary (i have to check that tomorrow). If i add a
.gitattribute file i have the
On Mon, Jul 24, 2017 at 07:11:06AM +0200, tonka tonka wrote:
> I have a problem with an already committed file into my repo. This git
> repo was converted from svn to git some years ago. Last week I have
> change some lines in a file and I saw in the diff that it is marked as
> binary (it's a
Hey everybody,
I have a problem with an already committed file into my repo. This git
repo was converted from svn to git some years ago. Last week I have
change some lines in a file and I saw in the diff that it is marked as
binary (it's a simple .cpp file). I think on the first commit it was
6 matches
Mail list logo