git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>, <email@mateuszwielgos.com>
Cc: '韩仰' <hanyang.tony@bytedance.com>, git@vger.kernel.org
Subject: RE: [External] Using Git as a Database
Date: Mon, 23 Sep 2024 15:09:22 -0400	[thread overview]
Message-ID: <00d001db0dec$1c8fa320$55aee960$@nexbridge.com> (raw)
In-Reply-To: <87r09aus7v.fsf@igel.home>

On September 23, 2024 2:43 PM, Andreas Schwab wrote:
>On Sep 23 2024, email@mateuszwielgos.com wrote:
>
>> Thank you for your reply, Han. The problem that I have with ‘—allow-empty’ is
>that the resulting commit is not associated with any particular file. I tried ‘git commit
>—allow-empty myfile.txt’ but the file argument is effectively ignored. ‘git log
>myfile.txt’ does not show the empty commit.
>
>Since the git model is snapshot based, there is no way around that, apart from
>putting the reference in the commit message which you can search with git log --
>grep=myfile.txt.

One way around this is to inject a date/timestamp in the file. Be careful about conflicts
If you every try to merge. This forces a signature change in the internal blob on
commit.

I am not recommending this, just suggesting a way to force the issue.


  reply	other threads:[~2024-09-23 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  3:28 Using Git as a Database Mateusz Wielgos
2024-09-23  3:48 ` [External] " 韩仰
2024-09-23 12:32   ` email
2024-09-23 18:42     ` Andreas Schwab
2024-09-23 19:09       ` rsbecker [this message]
2024-09-25 16:47 ` Sergey Organov

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='00d001db0dec$1c8fa320$55aee960$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=email@mateuszwielgos.com \
    --cc=git@vger.kernel.org \
    --cc=hanyang.tony@bytedance.com \
    --cc=schwab@linux-m68k.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).