incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <a...@shanecurcuru.org>
Subject Re: An svn question
Date Sat, 25 Jun 2011 11:10:13 GMT
Someone asked on another list how to change a log message in Subversion 
(for example, if you forgot to type in a log message on commit, or made 
typos).

See this excellent FAQ about Subversion from the Subversion developers:
   http://subversion.apache.org/faq.html#change-log-msg

I *think* our admins have this feature turned on, because I know other 
projects sometimes update missing log messages like this.

One note: the Apache Subversion project's FAQ to using Subversion is 
excellent, and may be a useful resource.  As you might expect, how the 
Apache Subversion community actually uses Subversion is a little 
different than most other projects, because most developers there are 
experts in Subversion. 8-)

For example, the Subversion recommendation is to send [PATCH]es inline 
in your email, not attached.  Basically, it's up to each individual 
project to decide how they want to handle the details of participation 
guidelines, like whether you prefer patch code inline or as attachments.

One key reminder about Subversion: remember to check your svn:eol-style 
settings in whichever Subversion client you use!  This takes care of 
most EOL issues when everyone does it correctly.

   http://www.apache.org/dev/version-control.html#https-svn-config

- Shane

On 6/23/2011 1:15 PM, Mathias Bauer wrote:
> Hi,
>
> I'm no svn expert, but I hope to find some here.
>
> We still have a lot of work in so called child workspaces (in Mercurial
> they are just an own repository that originates from the "main"
> repository). When I thought about possible ways to move them to the
> Apache repository, I had the idea that doing this as a patch might be
> the easiest way:
>
> - it's trivial to create a patch of a CWS containing all changes
> - the patch does not have any copyright problems as all changes in it
> are done by Oracle employees or by other developers under SCA
> - changes on problematic files will just not apply if the file is not in
> the basic svn repo of OOo
>
> Sounds like a good idea, doesn't it?
>
> But now I recognized that this idea was based on the wonderful feature
> that the "git extended" diff format offers. It allows to have file
> removal, addition or renaming (that includes moves in the tree) or file
> attribute changes in the diff and by using "hg patch" (and not the patch
> command of the OS) all these changes apply nicely in the target repository.
>
> I didn't find a support for this in svn, but maybe there is something
> similar or comparable we could use.
>
> Another option would be to commit the initial source code (the code that
> is directly retrieved from the software grant from Oracle) into a local
> Mercurial repository, add all the patches and then convert this into an
> svn repository.
>
> What do the experts say?
>
> Regards,
> Mathias

Mime
View raw message