git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.29.0-rc1
Date: Mon, 12 Oct 2020 09:35:25 -0700	[thread overview]
Message-ID: <xmqqimbfqu5u.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <e7b33ed0-b7e8-d14d-c97a-1fe13840ee29@web.de> (=?utf-8?Q?=22R?= =?utf-8?Q?en=C3=A9?= Scharfe"'s message of "Sun, 11 Oct 2020 08:11:11 +0200")

René Scharfe <l.s.r@web.de> writes:

> Am 10.10.20 um 18:45 schrieb René Scharfe:
>> Implementing hardlink support might be worthwhile anyway
>> and we would not even have to make it optional.
>
> It would be useful to have the contents duplicate blobs included only once
> in a tar file generated by git archive, but could have unexpected
> consequences.  Hard links would be extracted as such on platforms that
> support it.  Changing one of them might change all linked files, depending
> on the editor used.  That may be intended, but it could also be surprising.
> So this feature (if implemented) cannot be turned on unconditionally.

Good thinking.

  reply	other threads:[~2020-10-12 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 15:58 [ANNOUNCE] Git v2.29.0-rc1 Junio C Hamano
2020-10-10 16:45 ` René Scharfe
2020-10-11  6:11   ` René Scharfe
2020-10-12 16:35     ` Junio C Hamano [this message]
2020-10-12 16:33   ` Junio C Hamano
2020-10-12 19:19     ` René Scharfe
2020-10-24 17:52       ` René Scharfe
2020-10-26 18:01         ` Junio C Hamano

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=xmqqimbfqu5u.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    /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).