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

Re: git fast-export | git fast-import doesn't work

From
Ddavid@lang.hm <david@lang.hm>
Date
Nov 25, 2008, 23:53 UTC
Message-ID
<alpine.DEB.1.10.0811251548280.20120@asgard.lang.hm>
In-Reply-To
<85b5c3130811251539n6cb175b4p185d37385bf43d1e@mail.gmail.com>
On Wed, 26 Nov 2008, Ondrej Certik wrote:
Show 17 quoted lines
> On Tue, Nov 25, 2008 at 9:41 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
>> On Tue, Nov 25, 2008 at 06:31:41PM +0100, Michael J Gruber <git@drmicha.warpmail.net> wrote:
>>> I don't know, I just noticed that turning on rename and copy detection
>>> makes git-fast-import crash, which shouldn't happen either. Something's
>>> not right here. CC'ing the authors of im- and export.
>>
>> Could you please write a testcase that reproduces your problem?
>>
>>> Why export|import directly to git?
>>
>> I guess he did not know about filter-branch. :)
>
> I know about filter-branch (but I am not sure it can do what I want).
> I made a mistake of not explaining what I want, instead I suggested (a
> possibly wrong) solution. I want to export the whole git repository as
> a set of human readable patches, that can be assembled back into a git
> repository (with the same hashes as the original one)

the same hashes on the file is easy, the same hashes on the commits is extremely hard. which is it that you are looking for.

that being said, the test of being able to do a export|import is a good one to test that the export format and import format actually match.

David Lang
Show 28 quoted lines
> if needed. The
> reason I want that is that if we later decide to switch to another
> VCS, we have all the information to reproduce the repository. Another
> reason is to be sure that we know all the sources that are needed to
> construct the repository, e.g. that there are no binary blobs
> (possibly containing malicious code). Another reason I want that is to
> be able to rewrite the history, in particular, we have one Mercurial
> repository with some old history and another Mercurial history with a
> newer history and I just want to concatenate them together into one
> git repository.
>
> In each case I know several workarounds, but if there is a way to just
> convert the whole git repository into a set of patches and (and be
> able to convert everything back including the same hashes), then it'd
> be awesome.
>
> See also this thread why people want this (and I assumed git can do
> this from this thread):
>
> http://groups.google.com/group/sage-devel/browse_thread/thread/7b116d902ee20d9c/
>
> Thanks,
> Ondrej
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Previous: Ondrej CertikNext: Ondrej Certik
Message 5 of 25 in “git fast-export | git fast-import doesn't work”
  1. Ondrej CertikNov 25, 2008
  2. Michael J GruberNov 25, 2008
  3. Miklos VajnaNov 25, 2008
  4. Ondrej CertikNov 25, 2008
  5. david@lang.hmNov 25, 2008
  6. Ondrej CertikNov 25, 2008
  7. Peter BaumannNov 25, 2008
  8. Johannes SchindelinNov 26, 2008
  9. Ondrej CertikNov 26, 2008
  10. Ondrej CertikNov 26, 2008
  11. Michael J GruberNov 26, 2008
  12. Ondrej CertikNov 26, 2008
  13. Johannes SixtNov 26, 2008
  14. Ondrej CertikNov 27, 2008
  15. Ondrej CertikMay 3, 2009
  16. Johannes SchindelinNov 26, 2008
  17. Michael J GruberNov 26, 2008
  18. Johannes SchindelinNov 26, 2008
  19. Alexander GavrilovDec 7, 2008
  20. Johannes SchindelinDec 8, 2008
  21. Ondrej CertikNov 26, 2008
  22. Andreas EricssonNov 27, 2008
  23. Michael J GruberNov 26, 2008
  24. Johannes SchindelinNov 26, 2008
  25. Ondrej CertikNov 26, 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.