git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrew Ardill <andrew.ardill@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	Ben Olive <sionide21@gmail.com>,
	git@vger.kernel.org, Ben Walton <bdwalton@gmail.com>
Subject: Re: Super long branch names corrupt `.git/config`
Date: Fri, 5 Oct 2012 10:36:52 +1000	[thread overview]
Message-ID: <CAH5451=fEDd+EvgEst_G00nQ-yot+2UCbWt_UpduR57bhxHYew@mail.gmail.com> (raw)
In-Reply-To: <20121005002942.GB17586@sigill.intra.peff.net>

On 5 October 2012 10:29, Jeff King <peff@peff.net> wrote:
>...
>
>but it feels a little fake. Why 200? Because that will test the config
>limit, but will not overflow the NAME_MAX limit (at least not on
>Linux! No clue on other platforms) when we try to create
>refs/heads/foo-$z200.

I can't test this particular case right now, but I recently had an
issue with Windows Server 2008 due to a long filename, that
essentially meant I couldn't move, change owner or change permissions
on the given file. Unless someone has more info I can test a bit
later. Is the idea that we shouldn't allow filenames that will cause
issues with the underlying OS (or other people's OS) or something
else?

Regards,

Andrew Ardill

  reply	other threads:[~2012-10-05  0:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 17:15 Super long branch names corrupt `.git/config` Ben Olive
2012-10-04 18:29 ` Jeff King
2012-10-04 19:28 ` Junio C Hamano
2012-10-05  0:29   ` Jeff King
2012-10-05  0:36     ` Andrew Ardill [this message]
2012-10-05 15:38       ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH5451=fEDd+EvgEst_G00nQ-yot+2UCbWt_UpduR57bhxHYew@mail.gmail.com' \
    --to=andrew.ardill@gmail.com \
    --cc=bdwalton@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=sionide21@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).