Thanks for the advice.
I appreciate your help.
--- On Sat, 28/11/09, Ryan Schmidt <subversion-2009d_at_ryandesign.com> wrote:
> From: Ryan Schmidt <subversion-2009d_at_ryandesign.com>
> Subject: Re: Question about creating patch
> To: "Neo Anderson" <javadeveloper999_at_yahoo.co.uk>
> Cc: users_at_subversion.tigris.org
> Date: Saturday, 28 November, 2009, 2:08
> On Nov 27, 2009, at 19:17, Neo
> Anderson wrote:
>
> > I participate in a project which uses svn as its
> repository and I do not have previlege to commit source back
> to the svn. And I encounter a problem.
> >
> > Previously I alway use command `svn diff >
> /tmp/jira_number.patch` to create patch. There is no problem
> if I just modify existing source code. Now due to I create
> several java source files which previously did not exist in
> the svn repository, using `svn diff >
> /tmp/jira_number.patch` won't create patch that contains
> newly created source files. For instance, in svn there
> contained files
> >
> > messaging
> > + messagedriven + a.java/ b.java
> >
> > Now I add new files
> >
> > messaging
> > + messagdriven + a.java/ b.java/ c.java
> > + d.java
> > + e.java
> >
> >
> > Files like d.java, e.java and c.java won't be included
> in the jira_number.patch file if executing `svn diff >
> /tmp/jira_number.patch`. And I can't commit source so I
> can't do e.g. `svn add` to add source back to the
> repository.
> >
> > What is the better way (best practice) to create patch
> so the developers would be easier to apply or test patch?
>
> Either "svn add" the files first (that way they get
> included in the patch) or send the complete new files
> separately. Ask the project which way they prefer.
>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2425015
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-28 09:28:27 CET