public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: Gregory Stark <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Jim C. Nasby <[email protected]>
Cc: Mark Kirkwood <[email protected]>
Cc: Alvaro Herrera <[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: Wed, 16 May 2007 07:59:36 -0700
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 Wed, May 16, 2007 at 03:53:22PM +0100, Gregory Stark wrote:
> "David Fetter" <[email protected]> writes:
> 
> > On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote:
> >> Jim C. Nasby wrote:
> >> >BTW, is there some trick to getting cvs diff to ignore files
> >> >that aren't in the repo?
> >> 
> >> Trick? That's what it does by default.
> >
> > I suspect he's talking about all the lines starting with '?' that
> > diff produces.
> >
> > Lacking sophistication, I've been known to do:
> >
> > cvs diff [list of files here] |grep -v '^?' > the_file.diff
> 
> Those lines go to stderr.

Not when I do "cvs diff."  Is there something I should (un)set in my
.cvsrc?

> If you do "cvs diff > file" it spits out all the cvs file statuses
> to the terminal but dumps the diff to the file.
> 
> It doesn't matter, diffs can contain arbitrary junk between the file
> diffs.  patch only looks at the things it recognizes.

IMHO, the diffs also need to be human-readable, and 500 useless lines
starting with "?" don't help with that.

Cheers,
D
-- 
David Fetter <[email protected]> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666
                              Skype: davidfetter

Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate

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], [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