All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	dwmw2@infradead.org, git@vger.kernel.org
Subject: Re: Approxidate licensing
Date: Wed, 11 Oct 2006 00:55:01 -0700	[thread overview]
Message-ID: <7viriruw16.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0610101246241.9789@iabervon.org> (Daniel Barkalow's message of "Tue, 10 Oct 2006 13:39:47 -0400 (EDT)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> [1] git log and git blame are pretty impressive, but they don't quite 
> catch that most of date.c was written by David as part of commit-tree.c, 
> then Tony replaced it with a version that uses curl, then Edgar separated 
> it out into a date.c and simultaneously reverted Tony's changes. On the 
> other hand, the commit messages do say this, and you can use git log and 
> git blame to verify that they're true. The only thing they don't let 
> you verify is what the differences are between the date.c added in 
> ecee9d9e and the similar part of commit-tree.c in 812666c8. If someone 
> wants to make git blame *really* magic, date.c would be a good test case.

That's good to know.  I have in my head a super-duper blame that
I outlined in my obituary for git-annotate, but that is still a
vaporware and will continue to be for some time.

  parent reply	other threads:[~2006-10-11  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 17:39 Approxidate licensing Daniel Barkalow
2006-10-10 18:17 ` Linus Torvalds
     [not found] ` <1073a5540610101128q3fb9f68fsf3a28fbda20927d1@mail.gmail.com>
2006-10-10 18:33   ` Edesio Costa e Silva
2006-10-10 19:23 ` Junio C Hamano
2006-10-10 20:54   ` Junio's wishes [Was: Re: Approxidate licensing] Horst H. von Brand
2006-10-10 22:12     ` Linus Torvalds
2006-10-11  7:55 ` Junio C Hamano [this message]
2006-10-11  7:57 ` Approxidate licensing David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7viriruw16.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=barkalow@iabervon.org \
    --cc=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.