git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kevin Swinton <kevin.swinton@gmail.com>
To: git@vger.kernel.org
Subject: git - file types / metadata
Date: Fri, 21 Feb 2020 08:39:31 +0000	[thread overview]
Message-ID: <CAEwB0hh_Kifi4G6zqFJhM0aGzm+FqftvnavMkKqoxFph80PTjg@mail.gmail.com> (raw)

Hi

Currently converting git (using libgit2) to run on the RISC OS
operating system. There's one specific requirement this OS provides
that, after discussion with the libgit2 folk, I'd be grateful for your
expertise and experience on:

The RISC OS filesystem is not Unix-like. It doesn't use file
extensions like ".txt", but instead associates a 12-bit file type with
each file, to identify what sort of file it is (e.g. 0xfff=text file)

So the filemode value in a tree entry doesn't really apply. I can see
libgit2 uses a uint16_t to store this, and it appears to be written
into the object database in text form, so for a normal file in a tree
object, if I dump it on-screen I see this ASCII sequence: 100644.

Here's the thought: could git introduce some form of "custom" filemode
identifier? For example, a value of 017xxxx could be used to indicate
to git that it's to be treated the same as 0100644, but that those
bottom 12 bits of the filemode could be interpreted differently (in
this case with RISC OS it would actually provide exactly what's
needed).

(Feedback from libgit2 folk is that in future some kind of file
metadata ability - more general than this - could have other uses.)

Any thoughts/feedback/clarity on git policy, appreciated

regards

Kevin Swinton

                 reply	other threads:[~2020-02-21  8:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAEwB0hh_Kifi4G6zqFJhM0aGzm+FqftvnavMkKqoxFph80PTjg@mail.gmail.com \
    --to=kevin.swinton@gmail.com \
    --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.
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).