git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: PFDuc <pierre-francois.duc@mail.mcgill.ca>
To: Stefan Beller <sbeller@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git issue report : issue with capital letter in folder name
Date: Thu, 17 Dec 2015 18:35:25 -0500	[thread overview]
Message-ID: <567346BD.50703@mail.mcgill.ca> (raw)
In-Reply-To: <CAGZ79kbi-qdaNorabfZkFFL=FDZSgD332+N8bUrqfvu621EYvA@mail.gmail.com>

Le 2015-12-17 13:29, Stefan Beller a écrit :
> On Thu, Dec 17, 2015 at 7:45 AM, PFDuc
> <pierre-francois.duc@mail.mcgill.ca> wrote:
>> Hello,
>>
>> first of all thank you for developping git !
>>
>> I had an issue with a capital block in the folder name inside my git repo.
>> The folder in my local was named "Display" and the one at origin was named
>> "display" resulting in error when importing python code from this folder for
>> users who got the repo from origin.
> By any chance, were different operating systems or file systems
> involved in creation of
> this problem?
It might be the case, a mix between windows7, ubuntu and macOS
> There are file systems which care about the capitalization, and others don't.
> So if you have a file system which doesn't care about capitalization
> of the folder/file name,
> you can use a different capitalization and it still works. If you take
> the code to
> another system then, which is a bit more careful there are problems of course.
>
> The main question which remains, is how is Git involved? i.e. would it
> also happen
> if you just transfer a tarball? Did Git itself break anything?
I don't think git broke anything it is just that the folder name was not 
being changed to the one with a capital letter when I pushed on origin, 
the only way out I found was the one I described in my initial email. I 
thought then the problem might occur from git, but as you say it is 
probably a cross platform issue. The folder initially created was named 
display, then I changed it locally but git wouldn't recognize it as 
something to commit (platform windows7)

I just wanted to let you know in case it would have been an issue you 
wouldn't be aware of.

Regards,

Pierre-François
>> I tried to change the folder name on bitbucket.org but I was unable to (or
>> wasn't smart enough to find how to).
>>
>> I fixed the issue by deleting the file from my local, then commit, then
>> push, put the same folder in my local, then commit then push.
>>
>> I am therefore only writing to tell you that story which is not so
>> important, but I had the thought that because it is not so important maybe
>> nobody reports that and the bug (if any) cannot be fixed.
>>
>> Have a good day and happy end of year season!
>>
>> Regards,
>>
>> Pierre-François Duc
>> PhD candidate Physics McGill university
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-12-17 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 15:45 Git issue report : issue with capital letter in folder name PFDuc
2015-12-17 18:29 ` Stefan Beller
2015-12-17 23:35   ` PFDuc [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=567346BD.50703@mail.mcgill.ca \
    --to=pierre-francois.duc@mail.mcgill.ca \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    /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).