From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.org>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Anthony Sottile <asottile@umich.edu>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: windows: error cannot lock ref ... unable to create lock
Date: Mon, 24 Jun 2019 12:40:58 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1906241240450.44@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <98e1e1e5-c410-caf1-0e2f-9cb0cc6d7e94@iee.org>
Hi Philip,
On Sat, 22 Jun 2019, Philip Oakley wrote:
> On 18/06/2019 18:01, Eric Sunshine wrote:
> > On Tue, Jun 18, 2019 at 12:39 PM Anthony Sottile <asottile@umich.edu> wrote:
> > > + git fetch origin --tags
> > > Unpacking objects: 100% (10/10), done.
> > > From https://github.com/asottile-archive/git-windows-branch-test
> > > * [new branch] master -> origin/master
> > > error: cannot lock ref 'refs/remotes/origin/pr/aux': Unable to create
> > > 'C:/Users/IEUser/x/x/.git/refs/remotes/origin/pr/aux.lock': No such
> > > file or directory
> > > ! [new branch] pr/aux -> origin/pr/aux (unable to update local
> > > ref)
> > AUX is a reserved[1] filename on Windows. Quoting from that source:
> >
> > Do not use the following reserved names for the name of a file:
> > CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7,
> > COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and
> > LPT9. Also avoid these names followed immediately by an
> > extension...
> >
> > The default Git "ref store" is filesystem-based, so a branch named
> > "aux" is problematic. Other ref store implementations would not be
> > subject to this limitation (though I'm not sure what the state of the
> > others is -- someone with more knowledge can probably answer that).
> >
> > [1]:
> > https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#naming-conventions
> This sounds interesting. I thought (but I'm not certain) that Git for Windows
> avoided creating files in the working tree with such problematic names, so
> that a clone of a repo that contained a file "AUX" (any case, any extension
> IIRC), would be bypassed with possibly a warning message.
>
> However this looks to be a slightly different case where a _branch_ called
> "AUX" (lower cased) has been created within the clone, and it's a problem not
> trapped. Maybe worth creating a proper issue on the Git-for-Windows repo. Also
> cc'ing Dscho who may remember better than I.
He doesn't ;-)
Ciao,
Dscho
prev parent reply other threads:[~2019-06-24 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 16:38 windows: error cannot lock ref ... unable to create lock Anthony Sottile
2019-06-18 16:41 ` Anthony Sottile
2019-06-18 17:01 ` Eric Sunshine
2019-06-18 17:19 ` Anthony Sottile
2019-06-22 11:24 ` Philip Oakley
2019-06-24 10:40 ` Johannes Schindelin [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
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=nycvar.QRO.7.76.6.1906241240450.44@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=asottile@umich.edu \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=sunshine@sunshineco.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).