You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by xi...@niva.hu on 2004/08/17 22:13:39 UTC

release patches

Hi all!

I'm new to subversion, and would like to do the following:

There is a project maintained by someone else. This project is developed
continuosly, independent of me. I make unofficial patches for this project.
What is the easiest method for making patches for different versions of this
project?

Let's say there is pr1.0, pr1.1, pr1.2. I want to make changes in all of
them, and release my_pr1.0-patch, my_pr1.1-patch, my_pr1.2-patch. Also it is
more than likely that pr1.3 will be released. I'd like to maintain all these
version in the same svn.

How should I import pr1.0, pr1.1, pr1.2? How can I "switch over" to a
desired version and make the patches?

Thank you for your help,

Krisztian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: release patches

Posted by xi...@niva.hu.
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 ;-)

Krisztian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: release patches

Posted by kf...@collab.net.
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?
Have you read the Subversion book?

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.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: release patches

Posted by xi...@niva.hu.
On Wed, Aug 18, 2004 at 07:57:31AM -0500, kfogel@collab.net wrote:
> xian@niva.hu writes:
> > I'm new to subversion, and would like to do the following:
> > 
> > There is a project maintained by someone else. This project is developed
> > continuosly, independent of me. I make unofficial patches for this project.
> > What is the easiest method for making patches for different versions of this
> > project?
> > 
> > Let's say there is pr1.0, pr1.1, pr1.2. I want to make changes in all of
> > them, and release my_pr1.0-patch, my_pr1.1-patch, my_pr1.2-patch. Also it is
> > more than likely that pr1.3 will be released. I'd like to maintain all these
> > version in the same svn.
> > 
> > How should I import pr1.0, pr1.1, pr1.2? How can I "switch over" to a
> > desired version and make the patches?
> 
> Do you have commit access to the repository, and is it in Subversion?
> 
> If so, I recommend making branches (from their branches) and make your
> changes in your branches.  Then to give someone your patch, just point
> them to your branch.
> 
> -Karl
> 

Is it possible to maintain patches for pr1.0, pr1.1, pr1.2 at the same time?

Krisztian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: release patches

Posted by kf...@collab.net.
xian@niva.hu writes:
> I'm new to subversion, and would like to do the following:
> 
> There is a project maintained by someone else. This project is developed
> continuosly, independent of me. I make unofficial patches for this project.
> What is the easiest method for making patches for different versions of this
> project?
> 
> Let's say there is pr1.0, pr1.1, pr1.2. I want to make changes in all of
> them, and release my_pr1.0-patch, my_pr1.1-patch, my_pr1.2-patch. Also it is
> more than likely that pr1.3 will be released. I'd like to maintain all these
> version in the same svn.
> 
> How should I import pr1.0, pr1.1, pr1.2? How can I "switch over" to a
> desired version and make the patches?

Do you have commit access to the repository, and is it in Subversion?

If so, I recommend making branches (from their branches) and make your
changes in your branches.  Then to give someone your patch, just point
them to your branch.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org