{"thread":{"id":"8083","subject":"--stdin option for 'git log' [was FFmpeg considering GIT]","startedAt":"2007-05-11T11:13:45Z","lastAt":"2007-05-11T11:13:45Z","messageCount":1,"participants":["Marco Costalba"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"41825","messageId":"e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@mail.gmail.com","threadId":"8083","inReplyTo":null,"subject":"--stdin option for 'git log' [was FFmpeg considering GIT]","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-05-11T11:13:45Z","receivedAt":"2007-05-11T11:13:45Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 5/8/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:\n>\n> Well, we actually do have that. \"git log\" (or \"git-rev-list\") really does\n> all the heavy lifting. The reason you can do things like \"gitk --merge\" is\n> not because gitk itself has _any_ idea about anything, but because it just\n> passes the arguments down to git-rev-list (and hopefully soon git log),\n> which really does all the complex stuff.\n>\n\nTo replace 'git rev-list' with 'git log' an important missing feature,\nat least for me, is the support for '--stdin' option of 'git-rev-list'\nthat currently seems missing in 'git log'\n\nI found this limit while trying to use 'git log' instead of 'git\nrev-list'. The problem is that command line arguments could be very\nlong in some cases, typically when passing a list of sha's values (as\nexample all the branches sha). This happens of course when 'git log'\nis run by script/applications not directly by the user.\n\nUnder Linux, command line arguments size limits are _normaly_ enough\n(you could have problems for repository with hundreds of\ntags/branches), but under *others* OS we are not so lucky.\n\nSo with '--stdin' you have an elegant solution to support any kind of\nrepository under any OS ignoring  the platform limit on command line\nlength.\n\n\n Marco\n"}]}