| Re: [mdht-dev] filenames too long |
|
Hi Axel, Which version of Git are you using? On 19/02/16 02:11, Axel Helmer wrote:
Tony, I had the same problem (windows limits path lengths to 255 chars) and tried the same solution that Sean proposed. But it didn´t work on my Windows (10) system. For me, a simple workaround solved the problem: Checking out the models directly unter 'C:\'. Best, Axel 2016-02-18 16:33 GMT+01:00 sean.muir@xxxxxxxxxxxxxxx <sean.muir@xxxxxxxxxxxxxxx>:Tony - I have not seen this issue and it appears to be limited to windows; not sure which version of GIT you are using but this is recommended as a work around git config --system core.longpaths true Thie file names are generated which is why you end up with such long names occasionally let us know if the above works thanks Sean On Feb 18, 2016, at 10:18 AM, Tony Schaller <tony.schaller@xxxxxxxxxxxx> wrote: Hi While cloning https://github.com/mdht/mdht-models I get the following errors: C:\src\GitHub> git clone https://github.com/mdht/mdht-models Cloning into 'mdht-models'... remote: Counting objects: 94252, done. remote: Total 94252 (delta 0), reused 0 (delta 0), pack-reused 94252 eceiving objects: 100% (94252/94252), 181.55 MiB | 7.06 MiB/s Receiving objects: 100% (94252/94252), 184.13 MiB | 7.19 MiB/s, done. Resolving deltas: 100% (79571/79571), done. Checking connectivity... done. error: unable to create file PublicHealthCaseReporting/generated/org.openhealthtools.mdht.uml.cda.phcr.chlamydiatrachomatis/src/org/openhealthtools/mdht/uml/cda/phcr/chlamydiatrachomatis/operations/ChlamydiatrachomatisPHCRClinicalInformationSectionOperations.java (Filename too long) error: unable to create file PublicHealthCaseReporting/generated/org.openhealthtools.mdht.uml.cda.phcr.chlamydiatrachomatis/src/org/openhealthtools/mdht/uml/cda/phcr/chlamydiatrachomatis/operations/ChlamydiatrachomatisPHCRTreatmentInformationSectionOperations.java (Filename too long) error: unable to create file PublicHealthCaseReporting/generated/org.openhealthtools.mdht.uml.cda.phcr.chlamydiatrachomatis/src/org/openhealthtools/mdht/uml/cda/phcr/chlamydiatrachomatis/operations/ChlamydiatrachomatisTreatmentGivenSubstanceAdministrationOperations.java (Filename too long) error: unable to create file PublicHealthCaseReporting/generated/org.openhealthtools.mdht.uml.cda.phcr.chlamydiatrachomatis/src/org/openhealthtools/mdht/uml/cda/phcr/chlamydiatrachomatis/operations/ChlamydiatrachomatisTreatmentNotGivenSubstanceAdministrationOperations.java (Filename too long) error: unable to create file PublicHealthCaseReporting/tests/org.openhealthtools.mdht.uml.cda.phcr.chlamydiatrachomatis.tests/src/org/openhealthtools/mdht/uml/cda/phcr/chlamydiatrachomatis/tests/ChlamydiatrachomatisTreatmentNotGivenSubstanceAdministrationTest.java (Filename too long) Checking out files: 100% (16080/16080), done. fatal: unable to checkout working tree warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry the checkout with 'git checkout -f HEAD' Please shorten the filenames, tanks! Regards, Tony _______________________________________________ mdht-dev mailing list mdht-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mdht-dev _______________________________________________ mdht-dev mailing list mdht-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mdht-dev --
Vadim Peretokin The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files. |