[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Returned mail: see transcript for details

From: Jay Levitt <lists-svn_at_shopwatch.org>
Date: 2006-01-11 18:57:52 CET

The original message was received at Wed, 11 Jan 2006 12:57:51 -0500
from office.home.jay.fm []

   ----- The following addresses had permanent fatal errors -----
    (reason: Can't create output)

   ----- Transcript of session follows -----
procmail: [19354] Wed Jan 11 12:57:52 2006
procmail: Assigning "LOGFILE=/log/procmail"
procmail: Opening "/log/procmail"
550 5.0.0 <users@subversion.tigris.org>... Can't create output

attached mail follows:

Bump: anyone wanna take a shot at splaining?

Jay Levitt wrote:
> A quick search shows a few mentions of using externals and selective "svn
> update" commands to achieve partial branches, but I still can't get my
> head around it.
> I have a development machine and two production machines, and I have /etc
> under svn's control. The vast majority of /etc is the same on both dev
> and production, so this works well.
> But dev also acts as a management server, so for instance, it runs dhcpd.
> I'd like to keep /etc/dhcpd.conf under svn control, for obvious reasons,
> but I never want it to show up on a production machine. And
> /etc/httpd.conf will always differ, yet I'd like to version-control both
> the production and dev copies.
> What, exactly, could I do to achieve that? Step 1 is to create
> repos/tags/dev and repos/tags/production, but how do I avoid having to
> merge each change in common files (say, /etc/bashrc) into both branches?
> Jay Levitt

  • message/delivery-status attachment: stored
Received on Wed Jan 11 19:11:48 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.