{"thread":{"id":"26892","subject":"git fast-import --export-marks flag","startedAt":"2011-03-28T16:16:23Z","lastAt":"2011-03-28T20:47:52Z","messageCount":4,"participants":["psantosl@codicesoftware.com","Shawn Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"164454","messageId":"4D90B457.9040607@codicesoftware.com","threadId":"26892","inReplyTo":null,"subject":"git fast-import --export-marks flag","fromName":"psantosl@codicesoftware.com","fromEmail":"psantosl@codicesoftware.com","sentAt":"2011-03-28T16:16:23Z","receivedAt":"2011-03-28T16:16:23Z","isPatch":false,"sender":{"key":"psantosl@codicesoftware.com","avatar":"https://gravatar.com/avatar/ad76e8fe9587bdb03eeb1c91f6b91ecdeb2f5a2953bfc0f52c39b2bf86d12fe3?d=mp&s=160"},"body":"Hi,\n\ngit fast-import --export-marks is able to export to a file the marks and\nits associated commit hashes created during import.\n\nSo far I've seen the marks are not the ones provided in the input but\nsome \"internal ones\" not related with the input.\n\nWouldn't it be much better, for import/export interop, if it kept the\noriginal marks?\n\nIt would be certainly easier to do incremental import/export with\nexternal systems not dealing with SHAs...\n\nThanks,\n\npablo\n"},{"id":"164455","messageId":"AANLkTinpZ=PjGpFozCAWscfms6uWBSO2y+XqCGGqB2KP@mail.gmail.com","threadId":"26892","inReplyTo":"4D90B457.9040607@codicesoftware.com","subject":"Re: git fast-import --export-marks flag","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2011-03-28T16:25:01Z","receivedAt":"2011-03-28T16:25:01Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"On Mon, Mar 28, 2011 at 09:16, psantosl@codicesoftware.com\n wrote:\n> git fast-import --export-marks is able to export to a file the marks and\n> its associated commit hashes created during import.\n>\n> So far I've seen the marks are not the ones provided in the input but\n> some \"internal ones\" not related with the input.\n>\n> Wouldn't it be much better, for import/export interop, if it kept the\n> original marks?\n>\n> It would be certainly easier to do incremental import/export with\n> external systems not dealing with SHAs...\n\nI don't know what you are looking at, but fast-import uses the same\nmark numbers that were supplied in the input stream inside of the\nexported marks file. Otherwise as you pointed out, the marks are\nuseless.\n\n-- \nShawn.\n"},{"id":"164460","messageId":"4D90BBC4.2000908@codicesoftware.com","threadId":"26892","inReplyTo":"AANLkTinpZ=PjGpFozCAWscfms6uWBSO2y+XqCGGqB2KP@mail.gmail.com","subject":"Re: git fast-import --export-marks flag","fromName":"psantosl@codicesoftware.com","fromEmail":"psantosl@codicesoftware.com","sentAt":"2011-03-28T16:48:04Z","receivedAt":"2011-03-28T16:48:04Z","isPatch":false,"sender":{"key":"psantosl@codicesoftware.com","avatar":"https://gravatar.com/avatar/ad76e8fe9587bdb03eeb1c91f6b91ecdeb2f5a2953bfc0f52c39b2bf86d12fe3?d=mp&s=160"},"body":"Hi Shawn,\n\n> I don't know what you are looking at, but fast-import uses the same\n> mark numbers that were supplied in the input stream inside of the\n> exported marks file. Otherwise as you pointed out, the marks are\n> useless.\n\nWell, they're useful to run subsequent imports reusing the marks\ngenerated on the first import.\n\nBut ok, it seems my marks are \"overflowing\":\n\n>cat fast-export.dat\nblob\nmark :1\ndata 7\nbar.c\n\nblob\nmark :2\ndata 7\nfoo.c\n\nreset refs/heads/master\ncommit refs/heads/master\nmark :1583217\nauthor unknown 1300813103 +0100\ncommitter unknown 1300813103 +0100\ndata 8\ninitial\nM 100644 :1 src/bar.c\nM 100644 :2 src/foo.c\n\ncommit refs/heads/master\nmark :1583219\nauthor unknown 1300813115 +0100\ncommitter unknown 1300813115 +0100\ndata 5\nmove\nfrom :1583217\nR \"src/bar.c\" \"dst/bar.c\"\nR \"src/foo.c\" \"dst/foo.c\"\n\nreset refs/heads/master\nfrom :1583219\n\nAnd the generated marks are:\n\n:1 d1fe62248992d88f286d03bde972932e0118bf3c\n:2 146a766f34eb1dfb6c4d7b19a45ddf49ef7e5d5b\n:1074276465 52f475aba140ca2d6f6eb8f47ef0cdb9d043fab5\n:1074276467 caf606bb7cc64bab818acbc52b40d545467ddafc\n\n\npablo\n"},{"id":"164494","messageId":"4D90F3F8.1020706@codicesoftware.com","threadId":"26892","inReplyTo":"4D90BBC4.2000908@codicesoftware.com","subject":"Re: git fast-import --export-marks flag","fromName":"psantosl@codicesoftware.com","fromEmail":"psantosl@codicesoftware.com","sentAt":"2011-03-28T20:47:52Z","receivedAt":"2011-03-28T20:47:52Z","isPatch":false,"sender":{"key":"psantosl@codicesoftware.com","avatar":"https://gravatar.com/avatar/ad76e8fe9587bdb03eeb1c91f6b91ecdeb2f5a2953bfc0f52c39b2bf86d12fe3?d=mp&s=160"},"body":"It's working on 1.7, was broken on 1.6\n\nThanks,\n\npablo\n\nOn 28/03/2011 18:48, psantosl@codicesoftware.com wrote:\n> Hi Shawn,\n> \n>> I don't know what you are looking at, but fast-import uses the same\n>> mark numbers that were supplied in the input stream inside of the\n>> exported marks file. Otherwise as you pointed out, the marks are\n>> useless.\n> \n> Well, they're useful to run subsequent imports reusing the marks\n> generated on the first import.\n> \n> But ok, it seems my marks are \"overflowing\":\n> \n>> cat fast-export.dat\n> blob\n> mark :1\n> data 7\n> bar.c\n> \n> blob\n> mark :2\n> data 7\n> foo.c\n> \n> reset refs/heads/master\n> commit refs/heads/master\n> mark :1583217\n> author unknown 1300813103 +0100\n> committer unknown 1300813103 +0100\n> data 8\n> initial\n> M 100644 :1 src/bar.c\n> M 100644 :2 src/foo.c\n> \n> commit refs/heads/master\n> mark :1583219\n> author unknown 1300813115 +0100\n> committer unknown 1300813115 +0100\n> data 5\n> move\n> from :1583217\n> R \"src/bar.c\" \"dst/bar.c\"\n> R \"src/foo.c\" \"dst/foo.c\"\n> \n> reset refs/heads/master\n> from :1583219\n> \n> And the generated marks are:\n> \n> :1 d1fe62248992d88f286d03bde972932e0118bf3c\n> :2 146a766f34eb1dfb6c4d7b19a45ddf49ef7e5d5b\n> :1074276465 52f475aba140ca2d6f6eb8f47ef0cdb9d043fab5\n> :1074276467 caf606bb7cc64bab818acbc52b40d545467ddafc\n> \n> \n> pablo\n"}]}