Thanks, but Johannes has already found the issue and given a solution.
Regardless, replying to the questions just for the note.
On Sun, 2017-08-20 at 04:33 -0400, Jeff King wrote:
> What does "git for-each-ref" say about which branches you _do_ have?
>
> Also, what platform are you on?
>
I use
On Sun, 2017-08-20 at 10:20 +0200, Johannes Sixt wrote:
> It is not Git's fault that your terminal converts an invalid UTF-8
> sequence (that your script produces) to �. Nor is it when you paste that
> character onto the command line, that it is passed as a (correct) UTF-8
> character.
>
On Sun, Aug 20, 2017 at 01:21:29PM +0530, Kaartic Sivaraam wrote:
> I made a small assumption in the script which turned out to be false. I
> thought the unicode prefixes I used corresponded to only two bytes.
> This lead to the issue. The unicode character '✓' corresponds to three
> characters
Am 20.08.2017 um 09:51 schrieb Kaartic Sivaraam:
I made a small assumption in the script which turned out to be false. I
thought the unicode prefixes I used corresponded to only two bytes.
This lead to the issue. The unicode character '✓' corresponds to three
characters and as a result instead
Hello all,
First of all, I would like to tell that this happened completely by
accident and it's partly my mistake. Here's what happened.
I recently started creating 'feature branches' a lot for the few
patches that I sent to this mailing list. To identify the status of the
patch corresponding
5 matches
Mail list logo
