git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: File versioning based on shallow Git repositories?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 13, 2018, 11:12 UTC
Message-ID
<nycvar.QRO.7.76.6.1804131157360.65@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
In-Reply-To
<86efjjmqsi.fsf@gmail.com>
Hi Kuba,
On Fri, 13 Apr 2018, Jakub Narebski wrote:
Show 8 quoted lines
> 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.

I just sent out a patch to add a deprecation warning.

Ciao, Dscho

Previous: Jakub NarebskiNext: Jakub Narebski
Message 8 of 9 in “File versioning based on shallow Git repositories?”
  1. Hallvard Breien FurusethApr 12, 2018
  2. Ævar Arnfjörð BjarmasonApr 12, 2018
  3. Hallvard Breien FurusethApr 12, 2018
  4. Ævar Arnfjörð BjarmasonApr 12, 2018
  5. Rafael AscensaoApr 12, 2018
  6. Hallvard Breien FurusethApr 12, 2018
  7. Jakub NarebskiApr 13, 2018
  8. Johannes SchindelinApr 13, 2018
  9. Jakub NarebskiApr 13, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.