One of my uses of CVS is to record various releases of software, to see
changes between them. For instance, is kind of interesting and educative to
have all releases of linux kernel since linux-0.01 in a CVS repository so
you can see how the kernel evolved through time. I try to keep the original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodolfo Schulz de Lima <[EMAIL PROTECTED]> writes:
> On Sun, Oct 26, 2003 at 12:59:48PM -0800, Mark D. Baushke wrote:
>
> > I have not tried to do it, but you might be able to use multiple vendor
> > branches by using the -b switch to import and then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Rodolfo,
I have not tried to do it, but you might be able to use multiple vendor
branches by using the -b switch to import and then have the vendor be
LINUX_0_01, LINUX_0_10
That is,
cvs import -b1.1.1 module LINUX_0_01 LINUX-0_01_x_RELEASE
On Sun, Oct 26, 2003 at 12:59:48PM -0800, Mark D. Baushke wrote:
> I have not tried to do it, but you might be able to use multiple vendor
> branches by using the -b switch to import and then have the vendor be
> LINUX_0_01, LINUX_0_10
I've already thought about this solution. It works, but IMHO
On Sun, Oct 26, 2003 at 02:07:36PM -0800, Mark D. Baushke wrote:
> If you have concrete suggestions or a good vision you wish to share on
> the future of cvs, please share them here.
Mainly those import issues are what bothers me most. I'll try to come up
with a concrete way of dealing with vendo
[ On Sunday, October 26, 2003 at 12:59:48 (-0800), Mark D. Baushke wrote: ]
> Subject: Re: Multilevel vendor branch import
>
> I have not tried to do it, but you might be able to use multiple vendor
> branches by using the -b switch to import and then have the vendor be
> LINUX_0
On Mon, Oct 27, 2003 at 01:22:23PM -0500, Greg A. Woods wrote:
> BTW, those are design limits, not bugs. They are caused by the way CVS
> tracks _the_ one vendor branch. The multiple vendor-branch hacks
I see, I've never considered them bugs. Just recently I 'discovered'
subversion (svn), a cvs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodolfo Schulz de Lima <[EMAIL PROTECTED]> writes:
> On Mon, Oct 27, 2003 at 01:22:23PM -0500, Greg A. Woods wrote:
> > BTW, those are design limits, not bugs. They are caused by the way CVS
> > tracks _the_ one vendor branch. The multiple vendor-br
On Mon, Oct 27, 2003 at 11:52:19AM -0800, Mark D. Baushke wrote:
> CVS is a more mature product and needs to move a bit more conservatively
> oriented when considering large changes in how it works. I suspect there
> will be a place for cvs even after svn 1.0 is released.
I know, it's easy to turn
The rename problem has been discussed at length in this forum, and
several methods have been discussed. I believe that the best way to
solve the problem is to add a layer of indirection in the translation
between working file and RCS file. The pointer to the RCS file would
be stored in a versione
On Sunday 26 October 2003 03:22 pm, Rodolfo Schulz de Lima wrote:
> For instance, is kind of interesting and educative to
> have all releases of linux kernel since linux-0.01 in a CVS repository so
> you can see how the kernel evolved through time.
What you've learned the hard way is that CVS ven
Mark D. Baushke writes:
>
> Between now and the release of svn 1.0, I believe it is possible to
> address a number of the perceived limitations of CVS, but we need to
> determine how such changes fit into the overall way that CVS works
> rather than just adding a series of hacks.
>
> If anyone ha
On Tue, Oct 28, 2003 at 02:37:21PM -0500, Ross Patterson wrote:
> But the good news is that it doesn't look like what you're trying to do is
> all that hard with normal CVS. Instead of trying to "cvs import" each
> release, try just checking the updated code in to CVS. Tag it where tags
> make
[ On Thursday, October 30, 2003 at 15:46:45 (-0200), Rodolfo Schulz de Lima wrote: ]
> Subject: Re: Multilevel vendor branch import
>
> On Tue, Oct 28, 2003 at 02:37:21PM -0500, Ross Patterson wrote:
> > But the good news is that it doesn't look like what you're trying to
14 matches
Mail list logo