public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim C. Nasby <[email protected]>
To: Mark Kirkwood <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: David Fetter <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: PostgreSQL Docs <[email protected]>
Cc: PostgreSQL Patches <[email protected]>
Subject: Re: [PATCHES] OS/X startup scripts
Date: Tue, 15 May 2007 19:29:36 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Tue, May 15, 2007 at 03:35:45PM +1200, Mark Kirkwood wrote:
> Alvaro Herrera wrote:
> >Mark Kirkwood wrote:
> >>Alvaro Herrera wrote:
> >
> >>>Except that it also includes diffs for generated files, which tend to be
> >>>huge.  To work around that you need to create a list of files to
> >>>exclude, and the whole thing (which was cumbersome already) starts to
> >>>get unmanageable.
> >>$ make maintainer-clean
> >>
> >>before the diff, which clears all those out.
> >
> >Yeah, but then if you make a mistake with the patch and have to build
> >again to retest, you have to wait the whole thing to compile, which can
> >be annoying.
> >
> 
> True - depends on the speed of your machine as to how annoying this 
> really is... (I'm using a PIII 1.26 GHz... takes 5 min with -O2 - good 
> excuse for a coffee etc).
> 
> However, as David brought up previously it is probably worth mentioning 
> several of the various CVS work-arounds in the docs, so people at least 
> get a good survey of the options - they can then choose whichever suits 
> their needs best.

+1...

BTW, is there some trick to getting cvs diff to ignore files that aren't
in the repo?
-- 
Jim Nasby                                      [email protected]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

view thread (30+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [PATCHES] OS/X startup scripts
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox