-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 12, 2008, at 9:47 AM, Alexandre Vassalotti wrote:
On Mon, May 12, 2008 at 9:24 AM, "Martin v. Löwis"
<[EMAIL PROTECTED]> wrote:
The idea was to replace the orignial module file with its stub.
However, the "svn copy" and edit process isn't t
> Hmm, that's interesting information. I suspect I could easily create
> more bugs than I solve by using it, but it's interesting to know
> nevertheless.
I've been trying to use for a few applications. The biggest short-coming
is that it won't work for all cases. In particular, for the following
o
2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > 1.0. There are still case folding bugs in 1.0 - I'm working on fixing
> > them. But there will never be a complete fix for this situation, as
> > it's simply not possible to checkout the exact svn layout of that
> > revision on a case-folding
> 1.0. There are still case folding bugs in 1.0 - I'm working on fixing
> them. But there will never be a complete fix for this situation, as
> it's simply not possible to checkout the exact svn layout of that
> revision on a case-folding system, it simply can't be supported
> (without name manglin
> Hmm, Guido's been at the time machine again :-)
>
>> svn log http://svn.python.org/projects/python/trunk | tail
>
> r2161 | guido | 1990-08-09 15:25:15 +0100 (Thu, 09 Aug 1990) | 2 lines
>
> Initial revision
>
> -
2008/5/12 Paul Moore <[EMAIL PROTECTED]>:
> 2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > Subversion's first release was in October 2000; it wasn't self-hosting
> > until 2001 :-)
>
> I assume it's pre-svn history, converted from CVS. Or I'm misreading
> something. Whatever, it's from
2008/5/12 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> Which version of mercurial are you using? I know that versions prior
> 1.0 had some bug with handling case-changes on case-insensitive
> filesystems.
1.0. There are still case folding bugs in 1.0 - I'm working on fixing
them. But there will
2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > Revision 63129 is not valid on case folding filesystems. In
> > particular, this horribly breaks using hg-svn to make a local mirror
> > of the Python repository:
>
> That would be a bug in hg-svn, right? Yes, the revision is not valid
> on c
On Mon, May 12, 2008 at 9:24 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > The idea was to replace the orignial module file with its stub.
> > However, the "svn copy" and edit process isn't the cause of the
> > problems. It is the fact that 2 files existed in the same directory
> > differ
> The idea was to replace the orignial module file with its stub.
> However, the "svn copy" and edit process isn't the cause of the
> problems. It is the fact that 2 files existed in the same directory
> differing only by a case-change.
I still don't understand. You wanted to replace the file with
On Mon, May 12, 2008 at 7:18 AM, Paul Moore <[EMAIL PROTECTED]> wrote:
> Revision 63129 is not valid on case folding filesystems. In
> particular, this horribly breaks using hg-svn to make a local mirror
> of the Python repository:
>
> >\Apps\HGsvn\hgimportsvn.exe -r 63120
> http://svn.python.
On Mon, May 12, 2008 at 3:49 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Well, I guess I really messed up on that one. So, do you have any idea
> > on how to revert the changes?
>
> If the changes where in a single revision N, do
>
> svn merge -rN:N-1 .
> svn commit -m "revert rN"
>
>
On Mon, May 12, 2008 at 3:40 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > When I rename a module I use "svn copy", since "svn remove" doesn't
> > pick up changes made to the "deleted" file. For example, here is what
> > I did for PixMapWrapper:
>
> You want to make changes to the deleted
> Revision 63129 is not valid on case folding filesystems. In
> particular, this horribly breaks using hg-svn to make a local mirror
> of the Python repository:
That would be a bug in hg-svn, right? Yes, the revision is not valid
on case-folding systems - but why should that break hg-svn? The tool
2008/5/12 Paul Moore <[EMAIL PROTECTED]>:
> Bazaar seems to be OK (ish) with this - it picks just one version to show.
It seems to be unable to find the history using either bzr log
Lib\socketserver.py or bzr log Lib\SocketServer.py, though (but bzr
log seems pretty unintuitive to me, so maybe I
2008/5/12 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> On Sun, May 11, 2008 at 5:29 PM, Alexandre Vassalotti
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I have been working the module renaming for PEP-3108, and I just
> > noticed that some buildbots are throwing errors while updating their
> Well, I guess I really messed up on that one. So, do you have any idea
> on how to revert the changes?
If the changes where in a single revision N, do
svn merge -rN:N-1 .
svn commit -m "revert rN"
If they span over several subsequent revisions, use N-k
instead. If they span over several revisi
> When I rename a module I use "svn copy", since "svn remove" doesn't
> pick up changes made to the "deleted" file. For example, here is what
> I did for PixMapWrapper:
You want to make changes to the deleted file? Why?
Regards,
Martin
___
Python-Dev ma
On Sun, May 11, 2008 at 5:29 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have been working the module renaming for PEP-3108, and I just
> noticed that some buildbots are throwing errors while updating their
> checkout. It seems the method I use for renaming modules hits a
> s
On Sun, May 11, 2008 at 3:38 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> On Sun, May 11, 2008 at 6:31 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> The PEP specifies the lib-old directory to hold the old case name so
>> that the svn rename won't lead to two files in the same directory. I
On Sun, May 11, 2008 at 6:31 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> The PEP specifies the lib-old directory to hold the old case name so
> that the svn rename won't lead to two files in the same directory. I
> was hoping that creating the stub in lib-old would allow a simple
> ``svn rename``
On Sun, May 11, 2008 at 3:16 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> On Sun, May 11, 2008 at 5:44 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
>> 2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
>>> When I rename a module I use "svn copy", since "svn remove" doesn't
>>> pick up change
On Sun, May 11, 2008 at 5:44 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
>> When I rename a module I use "svn copy", since "svn remove" doesn't
>> pick up changes made to the "deleted" file. For example, here is what
>> I did for PixMapWrapper:
>>
On Sun, May 11, 2008 at 11:45:03PM +0200, Georg Brandl wrote:
> In any case, how does SVN on Windows handle this situation, having two
> identical filenames -- except for case -- in one directory?
Very bad. It's completely confused. It can checkout one of the files and
commit the other.
Oleg.
Alexandre Vassalotti schrieb:
When I rename a module I use "svn copy", since "svn remove" doesn't
pick up changes made to the "deleted" file. For example, here is what
I did for PixMapWrapper:
svn copy ./Lib/plat-mac/PixMapWrapper.py ./Lib/plat-mac/pixmapwrapper.py
edit ./Lib/plat-mac/Pix
Sorry, should have gone to the list:
2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> When I rename a module I use "svn copy", since "svn remove" doesn't
> pick up changes made to the "deleted" file. For example, here is what
> I did for PixMapWrapper:
>
> svn copy ./Lib/plat-mac/PixMapWra
Hello,
I have been working the module renaming for PEP-3108, and I just
noticed that some buildbots are throwing errors while updating their
checkout. It seems the method I use for renaming modules hits a
subversion bug on certain platforms. The error thrown looks like this:
...
svn: In directory
27 matches
Mail list logo
