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

Re: [RFC PATCH] Support gitlinks in fast-import/export.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 19, 2008, 01:22 UTC
Message-ID
<alpine.DEB.1.00.0807190321040.3064@eeepc-johanness>
In-Reply-To
<20080718204338.GB27528@spearce.org>
Hi,
On Fri, 18 Jul 2008, Shawn O. Pearce wrote:
Show 16 quoted lines
> Alexander Gavrilov <angavrilov@gmail.com> wrote:
> 
> > 	I noticed that fast-export & fast-import cannot work with 
> > 	repositories using submodules: import complains about an invalid 
> > 	mode, and export fails while trying to open the SHA as a blob.
> > 
> > 	As I didn't see any particular reason for it to be so, I tried to 
> > 	implement support for gitlinks.
> > 
> > 	What I'm unsure of is, should fast-export try to reuse commit 
> > 	marks for gitlinks where it happened to recognize the object, or 
> > 	always output the SHA as it is stored in the tree?
> 
> Its unlikely that the commit objects are in the repository the export is 
> running in, so its unlikely you can use a mark.  Its fine to just always 
> output the SHA-1 I think.

Oh, I just realized that fast-import expects changes, instead of full snapshots.

So strike all my suggestions regarding gitlink marks.

Sorry, Dscho

Previous: Shawn O. Pearce
Message 6 of 6 in “Support gitlinks in fast-import/export.”
  1. Support gitlinks in fast-import/export.Alexander Gavrilov, Jul 18, 2008
  2. Johannes SchindelinJul 18, 2008
  3. Alexander GavrilovJul 18, 2008
  4. Johannes SchindelinJul 18, 2008
  5. Shawn O. PearceJul 18, 2008
  6. Johannes SchindelinJul 19, 2008

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.