From: Gerhard Wiesinger <lists@wiesinger.com>
To: Andrew Ruder <andy@aeruder.net>
Cc: git@vger.kernel.org, kusmabite@gmail.com,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: Global .git directory
Date: Tue, 4 May 2010 08:07:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1005040755360.12746@bbs.intern> (raw)
In-Reply-To: <20100504054040.GC13139@goomba>
On Mon, 3 May 2010, Andrew Ruder wrote:
> On Tue, May 04, 2010 at 07:07:08AM +0200, Gerhard Wiesinger wrote:
> I know it all seems nit-picky, but if you want to see your changes make
> it into git.git you're best off making it as EASY AS POSSIBLE for the
> reviewer to take your patch and apply it and be done with it. This just
> isn't possible without testcases, documentation updates, etc..
> Especially for feature additions (vs bug fixes) you really have to make
> life as simple (and normal) as possible for reviewers, maintainers,
> etc.. After all, it is a lot easier living without a feature than it is
> a documented bug-fix!
>
> Just a random lurker trying to help you out here!
Thnx for your feedback. Will rework some of the parts you mentioned.
I think such a strict process should be valid for final commits to the git
repository. But for a first patch ready for discussion I think one
shouldn't make such strict process rules. I think we are at the state
whether such a patch *might* be accepted and reviewers should look at the
content first to have a decision for digging further (e.g. rework some
parts of the patch) or for "ok this makes no sense at all". I think this
saves time of the reviewers and also my time (I could now make all the
formal stuff of the patch you mentioned but when there is something
fundamental wrong there e.g in concept all the work was useless when not
accepted. I think there should be agreement of the roadmap of a feature
and then a focus on formalism to finally commit a pathc. So I'm a fan of
discussion and incremental work to minimise useless and typically
frustrating effort.)
Ciao,
Gerhard
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2010-05-04 6:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:14 Global .git directory Gerhard Wiesinger
2010-04-27 9:59 ` Thomas Rast
2010-04-27 20:06 ` Gerhard Wiesinger
2010-04-27 20:26 ` Erik Faye-Lund
2010-04-28 5:33 ` Gerhard Wiesinger
2010-04-28 6:22 ` Tomas Carnecky
2010-04-28 20:03 ` Gerhard Wiesinger
2010-04-28 8:01 ` Alex Riesen
2010-04-28 20:10 ` Gerhard Wiesinger
2010-04-28 12:50 ` Erik Faye-Lund
2010-04-28 20:22 ` Gerhard Wiesinger
2010-05-04 5:07 ` Gerhard Wiesinger
2010-05-04 5:40 ` Andrew Ruder
2010-05-04 6:02 ` Andreas Ericsson
2010-05-04 6:07 ` Gerhard Wiesinger [this message]
2010-05-04 16:55 ` Junio C Hamano
2010-04-27 20:37 ` Jacob Helwig
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=alpine.LFD.2.00.1005040755360.12746@bbs.intern \
--to=lists@wiesinger.com \
--cc=andy@aeruder.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=trast@student.ethz.ch \
/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).