git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Johannes.Schindelin@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH] Cast things properly to handle >2G files.
Date: Wed, 17 Jun 2009 16:16:20 -0700	[thread overview]
Message-ID: <7v7hzae9iz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0906171543120.16802@localhost.localdomain> (Linus Torvalds's message of "Wed\, 17 Jun 2009 15\:45\:16 -0700 \(PDT\)")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Wed, 17 Jun 2009, Alfred M. Szmidt wrote:
>> 
>> I would suggest the following update to the DCO, it makes it more
>> general both to free software hackers, and open source hackers alike.
>
> And I would suggest that Junio just not take patches from people who 
> aren't able to read the existing DCO. It's not worth the pain. 
>
> 		Linus

Thanks for trying to reduce my load.  Very much appreciated.

Even though I am _not_ a nice person, I _am_ a practical one.  Before
stopping to pay attention to this thread, I'll quote from my response once
more to ask a simple yes-or-no questions to Alfred.

  Are you the original author of the patch, and have the right to submit
  it under the license "indicated in the file"?

  The overall license of git is GPLv2, and that is what applies to unless
  there is an explicit license term indicated in the file otherwise. We do
  have some code under different licenses in some parts of the system, but
  the files that you are touching are all GPLv2.

  Can you certify that your patch is yours and you have rights to make it
  part of git under the same terms as the original?  Or can you not?

So Alfred, "yes"?  or "no"?  If "yes", you can send a sign-off.

Of course you can choose not to even if the answer is "yes", but then we
can choose to ignore your patch, too; and in fact we probably have to.

  reply	other threads:[~2009-06-17 23:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 20:03 [PATCH] Cast things properly to handle >2G files Alfred M. Szmidt
2009-06-14 20:17 ` Johannes Schindelin
2009-06-15  2:43   ` Nicolas Pitre
2009-06-15  3:39   ` Alfred M. Szmidt
2009-06-15  4:06     ` Junio C Hamano
2009-06-15  8:45       ` Johannes Schindelin
2009-06-15  4:25     ` Linus Torvalds
2009-06-17 22:27       ` Alfred M. Szmidt
2009-06-17 22:45         ` Linus Torvalds
2009-06-17 23:16           ` Junio C Hamano [this message]
2009-06-18  0:22           ` Fix big left-shifts of unsigned char Linus Torvalds
2009-06-18  8:12             ` Johannes Schindelin
2009-06-18  8:21               ` Junio C Hamano
2009-06-18 16:08               ` Linus Torvalds
2009-06-18 16:45                 ` Johannes Schindelin
2009-06-18 17:15                   ` Linus Torvalds
2009-06-18 17:28                     ` Fix various sparse warnings in the git source code Linus Torvalds
2009-06-18 17:45                       ` Matthieu Moy
2009-06-18 17:52                         ` Linus Torvalds
2009-06-18 21:48                       ` Linus Torvalds
2009-06-17 22:51         ` [PATCH] Cast things properly to handle >2G files Linus Torvalds
2009-06-17 22:27       ` Alfred M. Szmidt
2009-06-17 22:48         ` Linus Torvalds

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7v7hzae9iz.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ams@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).