[DBIx-Class-Devel] Pull Request: topic/docs-pod-inherit

[Peter Rabbitson]

On Thu, Dec 13, 2012 at 11:49:28PM +0100, Alexander Hartmaier wrote:
> On Thu, Dec 13, 2012 at 7:44 PM, Peter Rabbitson <rabbit+dbic at rabbit.us>wrote:
> 
> > On Thu, Dec 13, 2012 at 12:26:14PM +0100, Alexander Hartmaier wrote:
> > > On Thu, Dec 13, 2012 at 7:22 AM, Peter Rabbitson <rabbit+dbic at rabbit.us
> > >wrote:
> > >
> > > > On Wed, Dec 12, 2012 at 05:21:53PM -0500, Brendan Byrd wrote:
> > > > > The topic/docfixes_pending branch is ready.  Some notes:
> > > >
> > > > Right. Branch pulled apart as follows. In the future *please* exercise
> > > > more discipline - separate your concerns into branches. While it
> > doesn't
> > > > take me too long to wrangle the patches, it is still a substantial
> > amount
> > > > of time. You can save this time `git checkout -b foo master`
> > > > It isn't that hard.
> > > >
> > > Can we phrase a policy like: 'every topic branch should only contain a
> > > single commit to keep different fixes/features separately merge-able'?
> >
> > And when a feature needs several commits to make sense what do we do? :)
> >
> I knew you would bring up something like this ;)
> Should we limit fixes to a single commit and see how it goes?
> 

I am against using technological/procedural means so that people can continue
not thinking. I rather complain over and over again until a) they start
thinking ahead or b) go away.

But that's my 2c. I am not the one who does (nor will) write the policies,
remwember? This is jnap's job (as he volunteered rather loudly) for next
month ;)

Cheers