public inbox for [email protected]  

help / color / mirror / Atom feed

From: Mark Kirkwood <[email protected]>
To: 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 13:54:56 +1200
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]>

Alvaro Herrera wrote:
> David Fetter wrote:
>> On Mon, May 14, 2007 at 03:31:40PM +1200, Mark Kirkwood wrote:
>>> David Fetter wrote:
>>>> cvs diff works just great until you want to add or remove a file
>>>> without write permissions to the CVS repository, i.e. when you've
>>>> checked out as anonymous.
>>>>
>>> I usually saved an untouched version of the tree to compare against,
>>> so something like:
>>>
>>> $ cvs diff -Nacr pgsql.orig pgsql
>>>
>>> gives a complete patch including added/deleted files. It is a bit
>>> primitive, but is pretty easy to do!
> 
> 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.
> 
> I do use the cvsup mirror myself which makes things so much easier and
> faster.
> 

Not so, you just do a

$ make maintainer-clean

before the diff, which clears all those out.

While maintaining a cvs mirror is also good, for a small piece of work 
(or a work on a well defined area of the code) this requires no fooling 
around with repositories at all (which is nice).

Cheers

Mark

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