From: "Reece Dunn" <msclrhd@googlemail.com>
To: "Simon Hausmann" <simon@lst.de>, Git <git@vger.kernel.org>
Subject: Re: State of Perforce importing.
Date: Wed, 19 Sep 2007 19:23:41 +0100 [thread overview]
Message-ID: <3f4fd2640709191123j64b53878vc96d785c13c3bca2@mail.gmail.com> (raw)
In-Reply-To: <20070919171243.GA23902@old.davidb.org>
On 19/09/2007, David Brown <git@davidb.org> wrote:
> On Wed, Sep 19, 2007 at 08:19:11AM +0200, Simon Hausmann wrote:
>
> >> An additional problem:
> >>
> >> - git-p4 doesn't preserve the execute permission bit from Perforce.
> >
> >Hmm, can you paste the output of
> >
> > p4 fstat //path/in/depot/to/file/that/is/imported/incorrectly
> >
> >? I'm interested in the type of the file that p4 reports.
>
> headType kxtext
>
> so the problem is that the git-p4 is only looking for an 'x' at the start.
> According to 'p4 help filetypes', we need to use execute for any of:
>
> cxtext, kxtext, uxbinary, and the others that start with 'x'.
>
> I think it would be sufficient to check the first or second character for
> an 'x'. I'll make a change and give it a try later today.
These are the old file types. If you read the output of `p4 help
filetypes`, the new way of specifying this is with file type
modifiers. Therefore, you also have things like text+x.
- Reece
next prev parent reply other threads:[~2007-09-19 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 19:30 State of Perforce importing David Brown
2007-09-18 6:58 ` Simon Hausmann
2007-09-18 7:27 ` Sam Vilain
2007-09-18 15:49 ` David Brown
2007-09-18 17:53 ` Reece Dunn
2007-09-18 23:19 ` David Brown
2007-09-19 0:20 ` Sam Vilain
2007-09-19 0:26 ` David Brown
2007-09-19 0:23 ` Sam Vilain
2007-09-19 21:20 ` Reece Dunn
2007-09-20 6:12 ` Dmitry Kakurin
2007-09-18 23:37 ` David Brown
2007-09-19 0:23 ` Sam Vilain
2007-09-19 0:27 ` David Brown
2007-09-19 6:19 ` Simon Hausmann
2007-09-19 17:12 ` David Brown
2007-09-19 18:23 ` Reece Dunn [this message]
2007-09-19 18:25 ` David Brown
2007-09-19 18:56 ` Reece Dunn
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=3f4fd2640709191123j64b53878vc96d785c13c3bca2@mail.gmail.com \
--to=msclrhd@googlemail.com \
--cc=git@vger.kernel.org \
--cc=simon@lst.de \
/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).