My question is how do you manage production branching over modules?
Like if I want to roll out project1 with uses module1 module2 and module3
and when I roll this out I want to create a production branch. is there a
way to also branch the included module? If not does anyone have a
solution for
Hi James,
I am not a cvs guru, but as a quick thought, I would suggest to look at
the "modules" administration files. In two words, it allows you to
create "pseudo module" (and few other things) that are made either from
other module of specific files contained in those modules. When you
checkout
Peschko, Edward <[EMAIL PROTECTED]> writes:
> hm.
>
> I have a .cvsignore file in each of my directories with the following entry:
>
> *~
>
> and yet when I say:
>
> cvs add file~
>
> it happily accepts the file, puts it in for committing. when I cvs
> commit, it commits the file.
>
> umm...
hm.
I have a .cvsignore file in each of my directories with the following entry:
*~
and yet when I say:
cvs add file~
it happily accepts the file, puts it in for committing. when I cvs commit, it commits
the file.
umm... shouldn't .cvsignore block these entries from being even processed?
Ed
I've had this same problem too about a month ago. It was a major pain to
work out how to fix.
Given what HEAD means, it should never make sense to run:
cvs up -rHEAD
and it should always make sense to use: "cvs up -A" instead.
Given that, can the "up -r" option refuse to take "HEAD" as a tag? HE
I think this problem is endemic to the whole checkout-merge-commit model.
Nor Eclipse nor any other tool will be able to handle this in CVS, although
maybe it could send CVS users notifications of commits, and automatically
run "cvs up" if it was guaranteed to generate no conflicts. There's a hook
On Tue, Jun 03, 2003 at 12:46:42PM +0300, Stephen Biggs wrote:
> I got it to work using another way which actually works better if you
> don't want to be so interactive (one press of the enter key instead of
> 3):
>
> $ cvs ci -m "line 1"'$\n'"line 2"'$\n'"line 3"
Yikes! Non-interactive it may b
Recently we have decided to move our code base to CVS to manage versions
and releases. We have a bit of a unique situation however. We produce
firmware and a single bit of code gets used across several displays.
For instance there might be:
Module1
Module2
Module3
Module4a \ Can only have eithe
Thanks, that what I was missing...
Carlos
El mar, 03 de 06 de 2003 a las 20:37, Xtian Xultz escribió:
> We create a symbol for unconnected pin, attached...
> The dimensions of the symbol rerspect our library.
>
>
> > And a last thing: I'm used to attach an unconnected symbol to a pin
> > which
On Tue, 2003-06-03 at 09:45, Larry Jones wrote:
> > [And why is 'HEAD' a sticky tag in the first place?]
>
> Because you did "cvs update -r HEAD". Any time you update to a specific
> revision, that revision becomes "sticky" in your working directory.
> It's not that the tag itself is sticky, rat
Elijah P Newren writes:
>
> At the risk of sounding really stupid (this has to have a simple
> solution), how do I remove the sticky tag of 'HEAD' from my files?
cvs update -a
> [And why is 'HEAD' a sticky tag in the first place?]
Because you did "cvs update -r HEAD". Any time you update to a
Peschko, Edward writes [in very long lines]:
>
> what's the protocol for debugging cvs, in particular 'cvs pserver'?
> I'd like to start 'cvs pserver' on the command line, ping it with
> requests, and break to see where the requests lead..
What I usually do is to run the problematic command in s
At the risk of sounding really stupid (this has to have a simple
solution), how do I remove the sticky tag of 'HEAD' from my files?
[And why is 'HEAD' a sticky tag in the first place?] A quick 'cvs
update -A' does _not_ seem to work.
Here's where I've tried to find an answer:
Google: I got a t
Venu Vadapalli writes:
>
> It happens to a lot of files in vendor release B and not for the locally added
> files. I know that they were not removed in release B.
That doesn't make any sense at all. Either you're doing something very
wrong (like having your -j options in the wrong order or not
14 matches
Mail list logo
