git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: git@vger.kernel.org
Subject: Re: 2 directories same spelling one directory is camel cased
Date: Thu, 13 Oct 2016 18:03:23 +0200	[thread overview]
Message-ID: <967e9ca6-1e0a-7995-6e11-a3f0f255f087@web.de> (raw)
In-Reply-To: <e0a3eb0590552c98638d486db8ad4a12@davidwbrown.name>

On 12.10.16 18:05, David Brown wrote:
> 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 ?




      reply	other threads:[~2016-10-13 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 16:05 2 directories same spelling one directory is camel cased David Brown
2016-10-13 16:03 ` Torsten Bögershausen [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=967e9ca6-1e0a-7995-6e11-a3f0f255f087@web.de \
    --to=tboegi@web.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).