From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Hallvard Breien Furuseth" <h.b.furuseth@usit.uio.no>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org
Subject: Re: File versioning based on shallow Git repositories?
Date: Fri, 13 Apr 2018 23:57:52 +0200 [thread overview]
Message-ID: <861sfin50f.fsf@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1804131157360.65@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (Johannes Schindelin's message of "Fri, 13 Apr 2018 13:12:34 +0200 (DST)")
Hello Johannes,
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Fri, 13 Apr 2018, Jakub Narebski wrote:
>> Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no> writes:
>>
>>> Also maybe it'll be worthwhile to generate .git/info/grafts in a local
>>> clone of the repo to get back easily visible history. No grafts in
>>> the original repo, grafts mess things up.
>>
>> Just a reminder: modern Git has "git replace", a modern and safe
>> alternative to the grafts file.
>
> Right!
>
> Maybe it is time to start deprecating grafts? They *do* cause problems,
> such as weird "missing objects" problems when trying to fetch into, or
> push from, a repository with grafts. These problems are not shared by the
> `git replace` method.
Also you can propagate "git replace" info with clone / fetch / push.
> I just sent out a patch to add a deprecation warning.
Thank you for this.
--
Jakub Narębski
prev parent reply other threads:[~2018-04-13 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 18:01 File versioning based on shallow Git repositories? Hallvard Breien Furuseth
2018-04-12 18:47 ` Ævar Arnfjörð Bjarmason
2018-04-12 19:36 ` Hallvard Breien Furuseth
2018-04-12 20:46 ` Ævar Arnfjörð Bjarmason
2018-04-12 21:07 ` Rafael Ascensao
2018-04-12 21:22 ` Hallvard Breien Furuseth
2018-04-13 8:52 ` Jakub Narebski
2018-04-13 11:12 ` Johannes Schindelin
2018-04-13 21:57 ` Jakub Narebski [this message]
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=861sfin50f.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=h.b.furuseth@usit.uio.no \
/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).