From: "Adam Kłobukowski" <adamklobukowski@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: Problem with S_IFGITLINK
Date: Wed, 24 Aug 2011 17:30:12 +0200 [thread overview]
Message-ID: <4E551904.303@gmail.com> (raw)
In-Reply-To: <4E550E03.3080104@drmicha.warpmail.net>
W dniu 24.08.2011 16:43, Michael J Gruber pisze:
> Adam Kłobukowski venit, vidit, dixit 24.08.2011 14:49:
>> Hello
>>
>> I'm trying to compile git on some very exotic u*ix flavor (FreeMiNT
>> anyone? :)) and I encountered problem with S_IFGITLINK.
>>
>> Unfortunately, on my system S_IFGITLINK = S_IFLNK, and it breaks build
>> in entry.c write_entry.
>>
>> Should I report a bug? (where?, I could not find any reference to
>> bugtracker on git pages)
>
> Yes. Here.
>
> A short log of the build break would be nice.
>
>> Can I fix it somehow? Can I change value of S_IFGITLINK to something else?
>
> From git's cache.h:
>
> /*
> * A "directory link" is a link to another git directory.
> *
> * The value 0160000 is not normally a valid mode, and
> * also just happens to be S_IFDIR + S_IFLNK
> *
> * NOTE! We *really* shouldn't depend on the S_IFxxx macros
> * always having the same values everywhere. We should use
> * our internal git values for these things, and then we can
> * translate that to the OS-specific value. It just so
> * happens that everybody shares the same bit representation
> * in the UNIX world (and apparently wider too..)
> */
>
> Time to implement that translation :|
I may try to implement it, but I my knowledge of Git internals is equal
to zero. If someone can point me what has to be done - I'll be gratefull.
AdamK
next prev parent reply other threads:[~2011-08-24 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 12:49 Problem with S_IFGITLINK Adam Kłobukowski
2011-08-24 14:43 ` Michael J Gruber
2011-08-24 15:30 ` Adam Kłobukowski [this message]
2011-08-24 23:15 ` Nguyen Thai Ngoc Duy
2011-08-24 14:57 ` Michael Schubert
2011-08-24 15:26 ` Adam Kłobukowski
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=4E551904.303@gmail.com \
--to=adamklobukowski@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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).