From: David Greene <dag@cray.com>
To: git@vger.kernel.org
Subject: git-subtree
Date: Wed, 04 Jan 2012 09:53:36 -0600 [thread overview]
Message-ID: <nngaa638nwf.fsf@transit.us.cray.com> (raw)
Hey all,
Avery Pennarun has suckered me into^W^W^Wasked me to submit his
git-subtree tool for inclusion into mainline. Apparently there was some
discussion about this at GitTogether.
I have a patch ready. It takes git-subtree from the current GitHub
master, fixes the tests to use the standard git test harness and updates
the build to recognize git-subtree.
How does the git community want the patch presented? Right now it's one
monolithic thing. I understand that isn't ideal but I don't think
incorporating the entire GitHub master history is necessarily the best
idea either.
So I'm looking for some guidance.
Thanks!
-Dave
next reply other threads:[~2012-01-04 16:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 15:53 David Greene [this message]
2012-01-05 11:28 ` git-subtree Ramkumar Ramachandra
2012-01-05 15:03 ` git-subtree David A. Greene
2012-01-05 15:32 ` git-subtree Ramkumar Ramachandra
2012-01-05 16:33 ` git-subtree David A. Greene
2012-01-06 1:53 ` git-subtree David A. Greene
2012-01-05 22:18 ` git-subtree David A. Greene
2012-01-05 15:47 ` git-subtree Jeff King
2012-01-05 16:26 ` git-subtree David A. Greene
2012-01-29 22:07 ` git-subtree David A. Greene
2012-01-30 16:56 ` git-subtree David A. Greene
2012-01-05 22:16 ` git-subtree David A. Greene
2012-01-05 15:53 ` git-subtree Junio C Hamano
2012-01-05 16:48 ` git-subtree David A. Greene
2012-01-05 22:19 ` git-subtree David A. Greene
-- strict thread matches above, loose matches on Subject: below --
2021-11-14 10:11 git-subtree tqfx su
2021-11-15 8:12 ` git-subtree Fabian Stelzer
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=nngaa638nwf.fsf@transit.us.cray.com \
--to=dag@cray.com \
--cc=git@vger.kernel.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 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).