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
