From: "Michał Walenciak" <kicer86@gmail.com>
To: Igor Djordjevic <igor.d.djordjevic@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: broken text encoding in commit author name
Date: Mon, 10 Apr 2017 21:01:12 +0200 [thread overview]
Message-ID: <1877970.a7lV4V9TVC@kicer> (raw)
In-Reply-To: <e1836f50-1318-b72f-5507-b395be02e88d@gmail.com>
Dnia niedziela, 9 kwietnia 2017 00:07:52 CEST Igor Djordjevic pisze:
> Hi Michał,
>
> For what it`s worth, looking at the timestamp of the broken commit
> example you`ve shown, could the problem be related to amending commits?
>
> If so, are you amending through the command line, or maybe using some
> tool (like "git-gui")...?
>
> There was a similar discussion recently[1], not sure if it`s related
> to your case.
>
> [1]
> https://public-inbox.org/git/CAEPqvoz8s=CVLABuXx-zOzryrXwr_cb39G2TYJvvF
> XRYzpCBFQ@mail.gmail.com/
>
> Regards,
> Buga
Hi,
yes indeed, that's the case. Amend from gui ruins my commits :)
regards
--
Michał Walenciak
gmail.com kicer86
http://kicer.sileman.net.pl
gg: 3729519
prev parent reply other threads:[~2017-04-10 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 20:30 broken text encoding in commit author name Michał Walenciak
2017-04-08 22:07 ` Igor Djordjevic
2017-04-10 19:01 ` Michał Walenciak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1877970.a7lV4V9TVC@kicer \
--to=kicer86@gmail.com \
--cc=git@vger.kernel.org \
--cc=igor.d.djordjevic@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).