git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 2 directories same spelling one directory is camel cased

From
Torsten Bögershausen <tboegi@web.de>
Date
Oct 13, 2016, 16:03 UTC
Message-ID
<967e9ca6-1e0a-7995-6e11-a3f0f255f087@web.de>
In-Reply-To
<e0a3eb0590552c98638d486db8ad4a12@davidwbrown.name>
On 12.10.16 18:05, David Brown wrote:
Show 13 quoted lines
> Howdy git gurus,
> 
> I have the dubious distinction of working with a remote repo (master) that has a class loader run-time error when cloned, built and executed.
> 
> The reason for the runtime issue is a directory hierarchical path has to directories (folders) with the same name spelling but one of the directories is camel-cased. The package names are the same.
> 
> The compiler doesn't care but the run-time class loader has an issue with the 2 'same like named' classes.
> 
> How to remove the offending directories and files at the locally cloned repo but not push 'deleted' directories and files back to origin/master the remote repo?
> 
> Please advise.
> 
> Regards.
This email did not resolve from here: David Brown <david@davidwbrown.name>

It is somewhat unclear, which issue the class loader has. What does git ls-files | grep -i "sameNameBitDifferent" say ?

What do you mean with "How to remove the offending directories" ?

Just run rm -rf "offending directories" ?

Or, may be git mv dir1 NewDir1

If you don't want to push, you don't have to, or what do I miss ?
Previous: David Brown
Message 2 of 2 in “2 directories same spelling one directory is camel cased”
  1. David BrownOct 12, 2016
  2. Torsten BögershausenOct 13, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.