From: David Brown <david@davidwbrown.name>
To: git@vger.kernel.org
Subject: 2 directories same spelling one directory is camel cased
Date: Wed, 12 Oct 2016 11:05:19 -0500 [thread overview]
Message-ID: <e0a3eb0590552c98638d486db8ad4a12@davidwbrown.name> (raw)
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.
next reply other threads:[~2016-10-12 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 16:05 David Brown [this message]
2016-10-13 16:03 ` 2 directories same spelling one directory is camel cased Torsten Bögershausen
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=e0a3eb0590552c98638d486db8ad4a12@davidwbrown.name \
--to=david@davidwbrown.name \
--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).