From: Avery Pennarun <apenwarr@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
"David A. Greene" <greened@obbligato.org>,
git@vger.kernel.org
Subject: Re: git-subtree Ready #2
Date: Fri, 24 Feb 2012 18:57:33 -0500 [thread overview]
Message-ID: <CAHqTa-1fbi5W7R2fLu3bp7Yuv_ZB9nxhgjHkLGuU8-V4016+JA@mail.gmail.com> (raw)
In-Reply-To: <7vobsox84l.fsf@alter.siamese.dyndns.org>
On Fri, Feb 24, 2012 at 3:56 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Avery Pennarun <apenwarr@gmail.com> writes:
>> Overall I agree that there's little benefit in preserving the history,
>> at least as far as I can see, *except* that some code changes were
>> submitted by people other than me and squashing those changes might
>> conceivably cause licensing confusion down the road.
>
> That is a good point, and it sounds like a good enough justification to
> merge with history, at least for me.
Should we filter-branch or rebase the history first, or just leave it as is?
Like I said, since I don't expect there to be any more back-and-forth
development, rebasing should be pretty harmless.
Avery
next prev parent reply other threads:[~2012-02-24 23:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 17:35 git-subtree Ready #2 David A. Greene
2012-02-11 18:03 ` Junio C Hamano
2012-02-11 19:22 ` David A. Greene
2012-02-15 4:30 ` David A. Greene
2012-02-15 5:08 ` Jeff King
2012-02-15 5:31 ` David A. Greene
2012-02-16 4:07 ` David A. Greene
2012-02-20 19:34 ` David A. Greene
2012-02-20 20:53 ` Jeff King
2012-02-20 23:14 ` Junio C Hamano
2012-02-21 5:37 ` David A. Greene
2012-02-21 6:34 ` Junio C Hamano
2012-02-21 7:10 ` Junio C Hamano
2012-02-21 8:44 ` Junio C Hamano
2012-02-21 9:07 ` Thomas Rast
2012-02-24 1:19 ` Avery Pennarun
2012-02-24 20:56 ` Junio C Hamano
2012-02-24 23:57 ` Avery Pennarun [this message]
2012-02-25 5:00 ` David A. Greene
2012-02-25 9:00 ` Junio C Hamano
2012-02-25 15:00 ` David A. Greene
2012-02-27 21:06 ` Junio C Hamano
2012-02-27 21:21 ` Jeff King
2012-02-27 21:23 ` Jeff King
2012-02-28 2:04 ` Jakub Narebski
2012-02-28 22:42 ` Avery Pennarun
2012-03-02 3:42 ` David A. Greene
2012-02-21 5:31 ` David A. Greene
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=CAHqTa-1fbi5W7R2fLu3bp7Yuv_ZB9nxhgjHkLGuU8-V4016+JA@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greened@obbligato.org \
--cc=peff@peff.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.
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 NNTP newsgroup(s).