[dev] imp/templates/menu/menu.inc (was main.inc)

[Brent J. Nordquist]

On Sun, 4 Feb 2001, Chuck Hagenbuch <chuck@horde.org> wrote:

> > if you copy the archive, and
> > then check out an old revision/branch, you'd end up with a copy of the new
> > file in that revision/branch also, wouldn't you?
>
> Hmm... at the worst, it means we need to mark the new file as deleted in that
> branch...

Unless I'm misunderstanding you, that would keep it from being checked out
at the tip of the branch... but you'd get the extra (new) file when
checking out a tagged release (e.g. HORDE_1_2_3) that wasn't there when
the release was originally tagged.  That's the problem I'm hoping we can
solve, because that's what causes the automatic patch generation to break.

-- 
Brent J. Nordquist <bjn@horde.org>
Yahoo!: Brent_Nordquist / AIM: BrentJNordquist / ICQ: 76158942



>From chuck@horde.org Date: Sun,  4 Feb 2001 16:49:28 -0500
Return-Path: <chuck@horde.org>
Mailing-List: contact dev-help@lists.horde.org; run by ezmlm
Delivered-To: mailing list dev@lists.horde.org
Received: (qmail 1194 invoked from network); 4 Feb 2001 21:50:23 -0000
Received: from r94aag005136.sbo-smr.ma.cable.rcn.com (HELO marina.horde.org) (209.6.192.126)
  by horde.org with SMTP; 4 Feb 2001 21:50:23 -0000
Received: by marina.horde.org (Postfix, from userid 33)
	id C78193CA9; Sun,  4 Feb 2001 16:49:28 -0500 (EST)
Received: from 192.168.0.129 ( [192.168.0.129])
	as user chuck@marina by marina.your.mom with HTTP;
	Sun,  4 Feb 2001 16:49:28 -0500
Message-ID: <981323368.3a7dce688f14d@marina.your.mom>
Date: Sun,  4 Feb 2001 16:49:28 -0500
From: Chuck Hagenbuch <chuck@horde.org>
To: dev@lists.horde.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs
Subject: Re: [dev] imp/templates/menu/menu.inc (was main.inc)

Quoting "Brent J. Nordquist" <bjn@horde.org>:

> Unless I'm misunderstanding you, that would keep it from being checked out
> at the tip of the branch... but you'd get the extra (new) file when
> checking out a tagged release (e.g. HORDE_1_2_3) that wasn't there when
> the release was originally tagged.  That's the problem I'm hoping we can
> solve, because that's what causes the automatic patch generation to break.

I think I wasn't being clear. If you:

1. copy the ,v file
2. cvs delete the new file in all _old_ branches

I'm pretty sure you wouldn't get the file if it didn't have tags... but, I 
could be wrong, since I'm speculating and haven't actually gone ahead and tried 
it. :)

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"My intuitive grasp of math often leads me astray." -Me