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

Re: release patches

From: <xian_at_niva.hu>
Date: 2004-08-18 20:38:53 CEST

On Wed, Aug 18, 2004 at 10:11:13AM -0500, kfogel@collab.net wrote:
> xian@niva.hu writes:
> > Is it possible to maintain patches for pr1.0, pr1.1, pr1.2 at the same time?
> It's not possible to answer the question, not enough detail in the
> question, sorry.
> Are you an experienced Subversion user, or is this your first time?

What do you think? ;-) As I said before, I'm new.

> Have you read the Subversion book?

I'm reading it. Finally I found what I need: vendor branches.

> It's possible, and trivial, to maintain three patches just like
> maintaining any other three files in Subversion. It's hard to tell
> exactly what you're asking, though.
> If the question is, will Subversion automatically adjust the patches
> to apply to the different targets, the answer is no, it will not.

I want something like that... Let's say when I start to work I download
pr1.0, import it, and start to modify. Later the vendor releases pr1.1, and
I commit it (as described in the book). And I keep on working, modifying.
Naturally I'll be able to produce patch for version 1.1, but will it be
possible to create patch for 1.0 (after commiting 1.1)? This would be some
kind of "automated backporting"...

Thank you for your answers ;-)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 18 20:39:47 2004

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.