You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Daniel John Debrunner <dj...@debrunners.com> on 2004/09/23 18:51:41 UTC
My mistake - commit 47110
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Now I have commit access, my first commit goes wrong :-(
I was trying to just set the line ending style to native on a single
file to see if that solves tha svn diff/patch problems I see between
windows and linux. Instead of changing in that single file
(BUILDING.txt) I checked in all the other modified files in my view,
which include a patch from Jan and my changes to make the svn revision
number part of the versioning scheme.
The reason is that the svn commit works the opposite to perforce's p4
submit that was used for Cloudscape. In the edit window for a commit in
SVN you leave the lines for files you do not want to change, in perforce
you leave the lines for files you do want to change!
I'll figure out how to back out the change and make sure those changes
go through the correct process.
Sorry,
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBUv8dIv0S4qsbfuQRAqEkAKC8dA2qUIILdm2cAcQ6IvqpsSui4ACfQoFZ
zioAt9DHlC5/7nIVx8BTofk=
=6kVy
-----END PGP SIGNATURE-----
Re: My mistake - commit 47110
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel John Debrunner wrote:
> Daniel John Debrunner wrote:
>>The reason is that the svn commit works the opposite to perforce's p4
>>submit that was used for Cloudscape. In the edit window for a commit in
>>SVN you leave the lines for files you do not want to change, in perforce
>>you leave the lines for files you do want to change!
>
>
> I think I'm wrong on this, svn commit seems to always commit all the
> changes in your client, I don't see (yet) a way to commit only a sub-set
> of the files that you have modified. Does anyone know if this is possible?
OK, so you can specify the files to commit on the svn commit command
line, e.g.
svn commit foo.java bar.java
The editor window that is popped up is only for the commit description,
does not affect the files to commit. (Unlike Perforce)
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBUwpyIv0S4qsbfuQRAr7HAJoCwOKRsXR5iiMr5zn08hCGme+DPgCfcT4J
6Jyamtp4zDPZyVntbt/wA48=
=rhrT
-----END PGP SIGNATURE-----
Re: My mistake - commit 47110
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel John Debrunner wrote:
> Now I have commit access, my first commit goes wrong :-(
>
That change has been reverted in commit 47111
>
> The reason is that the svn commit works the opposite to perforce's p4
> submit that was used for Cloudscape. In the edit window for a commit in
> SVN you leave the lines for files you do not want to change, in perforce
> you leave the lines for files you do want to change!
I think I'm wrong on this, svn commit seems to always commit all the
changes in your client, I don't see (yet) a way to commit only a sub-set
of the files that you have modified. Does anyone know if this is possible?
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBUwUJIv0S4qsbfuQRAkqwAKCKeTt+7FQAq36uCPzD3LEKmH4iAwCfSlfM
2J0wiEjpSx4CoY2/gTGeuoc=
=O3Ui
-----END PGP SIGNATURE-----
RE: My mistake - commit 47110
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I was trying to just set the line ending style to native
Are you trying to change the file or set the property?
FOR ALL DERBY DEVELOPERS: if you have not been told about the Subversion
book, I urge to read the online edition: http://svnbook.red-bean.com/.
There will also be a Subversion tutorial and other sessions at ApacheCon
2004. I hope to see many of you there. :-)
--- Noel