git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Alexandre Badez <alexandre.badez@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Misspelled directory
Date: Mon, 19 May 2014 10:28:28 -0400	[thread overview]
Message-ID: <20140519142827.GA20289@sigill.intra.peff.net> (raw)
In-Reply-To: <CALQBTK_JchndNSd6ey746vY=N2TiHUc0Z1PJvp-vXYUZCkgc3Q@mail.gmail.com>

On Mon, May 19, 2014 at 03:05:42PM +0200, Alexandre Badez wrote:

> The '.' directory is not the same as the root directory; you can see
> that the /README.md and /./README.md are different.

Right. Inside git trees, "." as an entry name does not have any special
meaning. However, because it does have meaning in filesystems, git
itself will never create such an entry, and "git fsck" will warn about
it.

> I've reported the bug to stackedit (
> https://github.com/benweet/stackedit/issues/405
> ) who ignore it (not their fault).

GitHub normally blocks objects that do not pass "fsck" from being
pushed, but there are some loopholes when going through the API, which
stackedit does. I'll bring this one to the attention of the GitHub API
developers.

However, the end result will probably be GitHub rejecting the API
request from stackedit to create the bogus tree. So stackedit may end up
wanting to adjust their code to handle the situation more gracefully
anyway.

-Peff

      reply	other threads:[~2014-05-19 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 13:05 Misspelled directory Alexandre Badez
2014-05-19 14:28 ` Jeff King [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=20140519142827.GA20289@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=alexandre.badez@gmail.com \
    --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).