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 08:51:29 +0200 [thread overview]
Message-ID: <81b0412b0905112351l126a7c5bh902a7c7748d9a77a@mail.gmail.com> (raw)
In-Reply-To: <200905112208.21017.Hugo.Mildenberger@namir.de>
2009/5/11 Hugo Mildenberger <Hugo.Mildenberger@namir.de>:
> Using the mouse to paste a git url from a website into a terminal session in
> order to clone the repository, I recently managed to include invisible
> control characters into the git trunk directory name.
Git has no "trunk". Not in CVS/CVN sense, at least
> Consequently, I faced all sort of strange behaviour like git pull not working
> (error 2), later on a kernel make which supposedly could not finding a rule
> to create the trunk directory and more such inconsistencies.
> I then reinstalled git, rcs and so on and also tried unsuccessfully several
> git versions. The next morning I looked into the .git/config file and
> recognized that the "url" key value within the [remote "origin"] section
> contained some control characters: ^J and \n, as fas as I remember.
What platform are you on?
Can you show your .git/config?
> While this was almost entirely my fault, git could possibly apply a filter,
> reject such a name or at least issue a warning.
Maybe. Or maybe it can just work (well, assuming the user meant to
use an url with character you considered "control").
next prev parent reply other threads:[~2009-05-12 6:51 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 [this message]
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
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=81b0412b0905112351l126a7c5bh902a7c7748d9a77a@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).