From: Alex Riesen Date: Sat, 05 May 2007 18:03:00 GMT Subject: Re: [RFC?] Telling git about more complex relationships between commits (Was: Re: FFmpeg considering GIT) Message-ID: <20070505180300.GB2898@steel.home> In-Reply-To: <200705051449.45447.johan@herland.net> Johan Herland, Sat, May 05, 2007 14:49:42 +0200: > Can you categorically say that there is no use for the following output? > (even if you need to pass an option to "git blame" to get it): > ==== > ^bb0203a (User A 2007-05-05 12:25:44 +0200 1) foo > ^bb0203a (User A 2007-05-05 12:25:44 +0200 1) bar > ^bb0203a (User A 2007-05-05 12:25:44 +0200 3) baz > ==== Assuming a repo which has 50% of all commits - reverts (just because someone could not be bothered to learn to use rebase, format-patch and git-am before sending things upstream) I would use the exact wording I used before. I'd say "it's dangerous" now. It hides the mess this repo is. > > It's useless. > > Maybe. At least some of the fields I proposed are probably useless. But > I don't think we should throw away the core idea unless we can show > that _all_ fields are useless. Just think of something you actually _can_ use. Implement it and try. And than, if you are convinced it actually is useful, try it on your friends. And after them, if you're still alive, try using it with old git (like 1.4 from Debian and Ubuntu).