From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Gary V. Vaughan" <git@mlists.thewrittenword.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/5] General configuration portability (Resend)
Date: Fri, 12 Mar 2010 08:22:48 +0100 [thread overview]
Message-ID: <fabb9a1e1003112322l73cd8f93wffb1829f7988c22a@mail.gmail.com> (raw)
In-Reply-To: <20100312062308.GI7877@thor.il.thewrittenword.com>
Heya,
On Fri, Mar 12, 2010 at 07:23, Gary V. Vaughan
<git@mlists.thewrittenword.com> wrote:
> My employer kindly agreed to donate a little of my paid time to push
> the git patches we require to build on our supported hosts back
> upstream. There is certainly some good stuff in here that is useful
> outside of our environment, but I have another 1600 packages to port
> too...
While understandable, I hope your employer also understands that just
dumping a large patch upstream and tell them "have fun with it" does
not a good open source contribution make? Consider the time balance:
the investment required for us to figure out whether this patch is any
good for git, (not being familiar with the changes you're introducing,
and probably unable to test them since we lack the setup), and the
time it will cost you to split up the patches into an easily
reviewable series. I hope you (and your employer?) will agree that
it'd be less time for you to do so, than for us :).
Of course, if your employer is more like "pointy-haired boss" there's
not much you can do either.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2010-03-12 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 16:27 [PATCH 1/5] General configuration portability (Resend) Gary V. Vaughan
2010-03-11 16:51 ` Johannes Schindelin
2010-03-11 23:48 ` Brandon Casey
[not found] ` <1268326882-sup-9149@pinkfloyd.chass.utoronto.ca>
2010-03-12 6:23 ` Gary V. Vaughan
2010-03-12 7:22 ` Sverre Rabbelier [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fabb9a1e1003112322l73cd8f93wffb1829f7988c22a@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@mlists.thewrittenword.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).