From: Alex Riesen <raa.lkml@gmail.com>
To: Hugo Mildenberger <Hugo.Mildenberger@namir.de>
Cc: git@vger.kernel.org
Subject: Re: git fails with control characters in trunk directory name
Date: Tue, 12 May 2009 19:18:33 +0200 [thread overview]
Message-ID: <81b0412b0905121018lbccda1fvf6c4c19417cdde00@mail.gmail.com> (raw)
In-Reply-To: <200905121900.00625.Hugo.Mildenberger@namir.de>
2009/5/12 Hugo Mildenberger <Hugo.Mildenberger@namir.de>:
>> > Last not least, I managed to reproduce the problem almost exactly:
>> >
>> > 1.) hm@localhost git
>> > clone "git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-testing.git
>> > "
>> > (Note the trailing linefeed)
>>
>> That's all the command printed? No "Initialized empty Git repository" line?
>
> hm@localhost /var/tmp $ git clone "git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-testing.git
> "
> Initialized empty Git repository in /mnt/hda1/tmp/bluetooth-testing.git
> /.git/
> remote: Counting objects: 1177836, done.
> remote: Compressing objects: 100% (189467/189467), done.
> remote: Total 1177836 (delta 982785), reused 1176855 (delta 981880)
> Receiving objects: 100% (1177836/1177836), 288.16 MiB | 1288 KiB/s, done.
> Resolving deltas: 100% (982785/982785), done.
> Checking out files: 100% (27842/27842), done.
>
> hm@localhost /var/tmp $ ls
> bluetooth-testing.git? [Note that question mark replacing \n in repository's name]
>
Ok, clone works. Fully and correctly (even if a bit unexpected).
> hm@localhost /var/tmp/bluetooth-testing.git $ make
> make[1]: /mnt/hda1/tmp/bluetooth-testing.git: No such file or directory
> make[1]: *** No rule to make target `/mnt/hda1/tmp/bluetooth-testing.git'. Stop.
It is just linux build system which does not support compilation in oddly
named directories (which is reasonable, if you ask me).
> hm@localhost /var/tmp/bluetooth-testing.git $ git pull
> fatal: Error in line 2:
That's already fixed. Will send the fix in a minute.
next prev parent reply other threads:[~2009-05-12 17:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:08 git fails with control characters in trunk directory name Hugo Mildenberger
2009-05-12 6:51 ` Alex Riesen
2009-05-12 9:02 ` Hugo Mildenberger
2009-05-12 10:54 ` Alex Riesen
2009-05-12 13:57 ` Hugo Mildenberger
2009-05-12 14:59 ` Alex Riesen
2009-05-12 16:59 ` Hugo Mildenberger
2009-05-12 17:18 ` Alex Riesen [this message]
2009-05-12 17:24 ` [PATCH] Quote LF in urls git fetch saves in FETCH_HEAD Alex Riesen
2009-05-12 23:16 ` Junio C Hamano
2009-05-13 6:06 ` Alex Riesen
[not found] ` <200905131340.31509.Hugo.Mildenberger@namir.de>
2009-05-13 12:10 ` Alex Riesen
2009-05-13 14:49 ` Hugo Mildenberger
2009-05-13 12:39 ` Hugo Mildenberger
2009-05-13 15:18 ` Daniel Barkalow
2009-05-13 16:09 ` Alex Riesen
2009-05-13 17:07 ` Alex Riesen
2009-05-13 17:12 ` Daniel Barkalow
2009-05-13 18:11 ` Alex Riesen
2009-05-13 18:23 ` Junio C Hamano
2009-05-13 18:08 ` [PATCH 1/2] " Alex Riesen
2009-05-13 20:53 ` [PATCH 2/2] Improve the naming of guessed target repository for git clone Alex Riesen
2009-05-14 0:41 ` Junio C Hamano
2009-05-14 5:54 ` Alex Riesen
2009-05-14 6:35 ` Junio C Hamano
2009-05-14 8:45 ` Alex Riesen
2009-05-14 12:50 ` Hugo Mildenberger
2009-05-14 8:33 ` Alex Riesen
2009-05-16 17:49 ` Junio C Hamano
2009-05-12 17:41 ` git fails with control characters in trunk directory name Alex Riesen
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=81b0412b0905121018lbccda1fvf6c4c19417cdde00@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Hugo.Mildenberger@namir.de \
--cc=git@vger.kernel.org \
/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).