From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: Kenichi Asai <asai@is.ocha.ac.jp>, caml-list@inria.fr
Subject: Re: [Caml-list] On .gitignore
Date: Fri, 24 Mar 2017 12:16:10 +0000 [thread overview]
Message-ID: <CAHvkLrOuOseA_PGyDjGGKwzqfO17y=Y6ZXyUb9NddnN0cKw_Ew@mail.gmail.com> (raw)
In-Reply-To: <20170324070558.GA36798@pllab.is.ocha.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
Could you fill an issue on Mantis ? It's clearly a bug... A file in the
index should never be in the .gitignore.
--Fabrice
On Fri, Mar 24, 2017 at 8:06 AM Kenichi Asai <asai@is.ocha.ac.jp> wrote:
> Why is /otherlibs/systhreads/thread.ml listed in .gitignore in the
> OCaml distribution (or in the github repository)? Because of this,
> when I make a local git repository from the OCaml source and clone it
> to somewhere else, I get an error when I do "make world" because of
> the missing thread.ml file. Is it safe to remove the line from
> .gitignore?
>
> Peculiarly, when I modify thread.ml, "git status" reports that the
> file is modified, even though it is listed in .gitignore. I might not
> understand the behavior of .gitignore quite right.
>
> I found the following files exist and match .gitignore:
>
> .depend
> /otherlibs/systhreads/thread.ml
> testsuite/tests/asmcomp/mips.s
> testsuite/tests/opaque/intf/opaque_impl.mli
> testsuite/tests/opaque/intf/opaque_intf.mli
> testsuite/tests/opaque/intf/regular.mli
>
> --
> Kenichi Asai
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2805 bytes --]
next prev parent reply other threads:[~2017-03-24 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 7:05 Kenichi Asai
2017-03-24 12:16 ` Fabrice Le Fessant [this message]
2017-03-25 1:27 ` Kenichi Asai
2017-03-31 13:40 ` Sébastien Hinderer
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='CAHvkLrOuOseA_PGyDjGGKwzqfO17y=Y6ZXyUb9NddnN0cKw_Ew@mail.gmail.com' \
--to=fabrice.le_fessant@inria.fr \
--cc=asai@is.ocha.ac.jp \
--cc=caml-list@inria.fr \
/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).