Re: svn commit: rev 7223 - trunk/packages/rpm/mandrake-9.1
From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-09-29 00:44:06 CEST
Files <files@poetryunlimited.com> writes:
> Done - copy follows
When the change is spread over several files then start with a brief
"Update Madrake package build to add support for Java." or whatever
> * 46_mod_dav_svn.conf
* packages/rpm/mandrake-9.1/46_mod_dav_svn.conf
The HACKING guidelines say to use full path names, the other log
> (dav_svn_module,authz_svn_module): moved to <apache>-extramodules
Rev 7223 didn't change fop-gz, fop-bz2 or fop-installed, they should
* packages/rpm/mandrake-9.1/fop-file: Ignore ls error output.
>
* packages/rpm/mandrake-9.1/ge: Renamed to ge-0-30-0
I'm guessing that's what happened, your log message should tell me.
* packages/rpm/mandrake-9.1/just-docs: Removed, obseleted by eq1.
Neither increment-revision nor full-machine-name appear to have
>
* packages/rpm/mandrake-9.1/make-version-patch: Lots of things
machine-name and make-fo-patch don't appear to have been modified in
>
Didn't change in r7223, should not be mentioned.
>
Didn't change in r7223, should not be mentioned.
>
These didn't change in r7223, they should not be mentioned.
> * svn-install-silent-ge-0-31-0.patch
* packages/rpm/mandrake-9.1/svn-install-silent-ge-0-31-0.patch: New
> * svn-install-silent-ge-0-30-0.patch
These didn't change in r7223, they should not be mentioned.
> * svn-java.patch
* packages/rpm/mandrake-9.1/svn-java.patch: New file, containing patch
>
Can you explain why mandrake-9.1 has been changed but not 9.0 or 9.2?
I'm not really interested in Mandrake or Java, I tend to ignore the
I must admit I don't understand why you need to make such extensive
-- Philip Martin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Mon Sep 29 00:44:53 2003 |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.