git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Pat Thoyts <patthoyts@users.sourceforge.net>
Subject: Re: [PATCH/RFC] Replace Free Software Foundation address in license notices
Date: Mon, 13 Nov 2017 14:49:21 -0500	[thread overview]
Message-ID: <20171113194921.GP5144@zaya.teonanacatl.net> (raw)
In-Reply-To: <xmqqmv3wjd66.fsf@gitster.mtv.corp.google.com>

Junio C Hamano wrote:
> This change probably makes sense.  From here on after applying the 
> patch, we won't have to worry about updating these every time they 
> move---not that they have moved often, though ;-)

Indeed.  It's thankfully a rare move.  I imagine that's why it's 
somewhat common to find license text with the previous address long 
after the last move.  (That and how boring licensing details are, in 
general.)

>>  compat/obstack.c                                                | 5 ++--- 
>>  ... 
>>  ewah/ewok_rlw.h                                                 | 3 +-- 
>>  git-gui/git-gui.sh                                              | 3 +-- 
>>  imap-send.c                                                     | 3 +-- 
>>  ... 
>>  44 files changed, 69 insertions(+), 103 deletions(-)
>
> I've tried hard to keep the git-gui/ part as a separate project (it 
> indeed is managed separately).  I have been, and am still only 
> pulling from its "upstream" repository (Pat, who is its project 
> lead, Cc'ed), refaining from making changes that do not exist there 
> at git://repo.or.cz/git-gui.git/ to the tree I publish.
>
> I'll separate the part from this patch that touches git-gui/* and 
> try to arrange the next pull from git-gui repository would have the 
> omitted part somehow.  Given that the "upstream" seems to be inactive 
> these days, we might want to change the way we manage that part of 
> the tree, though.

D'oh, I should have known that.  Thanks for splitting this up.  I was 
worried more minor things like legal details or changing code that we 
synced from another project (compat/regex or xdiff) might require some 
changes and didn't think enough about git-gui being separate.

> Thanks.

Thank you too.  It's always impressive to see how well you wear the 
maintainer hat. :)

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A common mistake people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
    -- Douglas Adams


      reply	other threads:[~2017-11-13 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  5:39 [PATCH/RFC] Replace Free Software Foundation address in license notices Todd Zullinger
2017-11-09  4:20 ` Junio C Hamano
2017-11-13 19:49   ` Todd Zullinger [this message]

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=20171113194921.GP5144@zaya.teonanacatl.net \
    --to=tmz@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=patthoyts@users.sourceforge.net \
    /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).