From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Josh Triplett <josh@freedesktop.org>,
Jason Sewall <jasonsewall@gmail.com>,
Jamey Sharp <jamey@minilop.net>
Subject: Re: Breaking up repositories
Date: Fri, 1 Jun 2007 08:45:45 +0100 [thread overview]
Message-ID: <200706010845.45761.andyparkins@gmail.com> (raw)
In-Reply-To: <465EEF96.6050307@freedesktop.org>
On Thursday 2007 May 31, Josh Triplett wrote:
> We really need to fix some things in git-split and get it merged into git.
Obviously it's Junio's call, but can I suggest that getting it in the git tree
(presumably under contrib/) should not be dependent on fixing
whatever "things" you are worrying about? Waiting until it's perfect before
submitting it. As Voltaire said (I think), "better is the enemy of good".
Speaking from my own personal viewpoint, while I'm not a huge contributor to
git, I do fix the odd buglet here and there - and here's the rub - I only do
it to those files that are in the git tree.
While git-split is being maintained separately, I would argue that there are
less eyes on it. Get it in, regardless of state, at the very least it will
mean that git-split's development will be tracked as publicly as git.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-06-01 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 15:53 Breaking up repositories Josh Triplett
2007-06-01 7:45 ` Andy Parkins [this message]
2007-06-01 10:25 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 6:50 Jason Sewall
2007-05-31 13:55 ` Dave Hanson
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=200706010845.45761.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jamey@minilop.net \
--cc=jasonsewall@gmail.com \
--cc=josh@freedesktop.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).