{"thread":{"id":"16974","subject":"git-fast-export bundle doc","startedAt":"2009-01-03T00:52:35Z","lastAt":"2009-01-06T20:11:26Z","messageCount":4,"participants":["jidanni@jidanni.org","Miklos Vajna","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"99235","messageId":"87r63lus6k.fsf@jidanni.org","threadId":"16974","inReplyTo":null,"subject":"git-fast-export bundle doc","fromName":"","fromEmail":"jidanni@jidanni.org","sentAt":"2009-01-03T00:52:35Z","receivedAt":"2009-01-03T00:52:35Z","isPatch":false,"sender":{"key":"jidanni@jidanni.org","avatar":"https://gravatar.com/avatar/36568d4af4c8d3e71627ef3b8c8d00e39065b12f29676cccd38ced75e68fa2a6?d=mp&s=160"},"body":"Please improve git-fast-export.txt. It says\n\n This program dumps the given revisions in a form suitable to be\n piped into git-fast-import.\n\n isn't mentioned in the SYNOPSIS.\nAnd there is no hyperlink to the git-fast-import man page, nor in SEE ALSO.)\n\n You can use it as a human readable bundle replacement (see\n git-bundle(1))\n\nBut I tried it and there are apparently a few steps not mentioned that\nare needed after git-fast-import before you can actually see the files\nagain on the other side of the sneakernet.\n\nI used --all, which is in EXAMPLES but not OPTIONS.\n\nElse nothing happens and no error is caught:\n$ git fast-export\n$\n\nAlso the git-bundle man page should SEE ALSO git-fast-export and maybe\neven git-fast-import, which itself makes no mention of git-fast-export.\n"},{"id":"99239","messageId":"1230955152-23646-1-git-send-email-vmiklos@frugalware.org","threadId":"16974","inReplyTo":"87r63lus6k.fsf@jidanni.org","subject":"[PATCH] fast-export: print usage when no options specified","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-01-03T03:59:12Z","receivedAt":"2009-01-03T03:59:12Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nI found that behaviour surprising as well when I saw it the first time.\ngit rev-list outputs some usage info in that case, git log just logs\nHEAD. Given that unconditionally exporting HEAD with no arguments is\nprobably not something most users want, here is a patch to make the\nbehaviour like what git rev-list already has.\n\n builtin-fast-export.c | 3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/builtin-fast-export.c b/builtin-fast-export.c\nindex 8386338..e9ee2c7 100644\n--- a/builtin-fast-export.c\n+++ b/builtin-fast-export.c\n@@ -497,6 +497,9 @@ int cmd_fast_export(int argc, const char **argv, const char *prefix)\n \t\tOPT_END()\n \t};\n \n+\tif (argc == 1)\n+\t\tusage_with_options (fast_export_usage, options);\n+\n \t/* we handle encodings */\n \tgit_config(git_default_config, NULL);\n \n-- \n1.6.1\n"},{"id":"99494","messageId":"alpine.DEB.1.00.0901062023100.30769@pacific.mpi-cbg.de","threadId":"16974","inReplyTo":"1230955152-23646-1-git-send-email-vmiklos@frugalware.org","subject":"Re: [PATCH] fast-export: print usage when no options specified","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-01-06T19:28:59Z","receivedAt":"2009-01-06T19:28:59Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 3 Jan 2009, Miklos Vajna wrote:\n\n> Signed-off-by: Miklos Vajna \n> ---\n> \n> I found that behaviour surprising as well when I saw it the first time.\n> git rev-list outputs some usage info in that case, git log just logs\n> HEAD. Given that unconditionally exporting HEAD with no arguments is\n> probably not something most users want, here is a patch to make the\n> behaviour like what git rev-list already has.\n\nMaybe this should be part of the commit message?\n\n-- snip --\nSome people find it surprising that fast-export does not output a usage \nwhen called without parameters, as rev-list does.\n\nThis assumes that a user usually does not want to export HEAD by default.\n-- snap --\n\nHowever, I have to say that I would find exporting HEAD a rather sensible \ndefault.\n\nBut I am not _that_ strongly opposed to the patch. Just would like to \nhear some opinions first.\n\nCiao,\nDscho\n"},{"id":"99501","messageId":"20090106201126.GJ21154@genesis.frugalware.org","threadId":"16974","inReplyTo":"alpine.DEB.1.00.0901062023100.30769@pacific.mpi-cbg.de","subject":"Re: [PATCH] fast-export: print usage when no options specified","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-01-06T20:11:26Z","receivedAt":"2009-01-06T20:11:26Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Tue, Jan 06, 2009 at 08:28:59PM +0100, Johannes Schindelin wrote:\n> Maybe this should be part of the commit message?\n> \n> -- snip --\n> Some people find it surprising that fast-export does not output a usage \n> when called without parameters, as rev-list does.\n> \n> This assumes that a user usually does not want to export HEAD by default.\n> -- snap --\n\nOK, if this is the only problem, I can resend it with this included. ;-)\n\n> However, I have to say that I would find exporting HEAD a rather sensible \n> default.\n> \n> But I am not _that_ strongly opposed to the patch. Just would like to \n> hear some opinions first.\n\nAccording to man git, fast-export is not a plumbing, though I think most\nuser won't type it manually multiple times, they'll write a script, that\nchecks if there is something to convert, then run git fast-export | foo\nfast-import, so it's really like plumbing. That's why I found the\nrev-list-like behaviour more logical.\n\nHowever, I think defaulting to HEAD is still better than the current\nsituation, so if that's the consensus, I'm fine with that as well.\n"}]}