RE: [stellation-res] Windows Issues

["Jonathan Gossage" <jgossage@xxxxxxxx>]

>-----Original Message-----
>From: stellation-res-admin@xxxxxxxxxxxxxxx
>[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Mark C.
>Chu-Carroll
>Sent: August 20, 2002 2:48 PM
>To: stellation-res@xxxxxxxxxxxxxxx
>Subject: Re: [stellation-res] Windows Issues


>On Tuesday 20 August 2002 10:11 pm, Jonathan Gossage wrote:
>> >On Tue, Aug 20, 2002 at 09:38:19AM -0500, Florin Iucha wrote:
>> >> Windows file matching is case insensitive. However the file creation
is
>> >> case preserving. IE if I ask for "FooBar.txt" to be created, that is
the
>> >> name that windows will store in its metadata. However, I can open that
>> >> file by any variation of case in the file name: "foobar.txt",
>> >> "FOObar.Txt"...
>> >>
>> >> But we should preserve the filenames exactly as they are introduced,
not
>> >> for Windows sake, but for porting to other platforms of the code we
>> >> store in the repository.
>> >
>> >Right you are. We went through all this with Jikes, doing a walk through
>> >the file system metadata, finding the actual user spelling, making the
>> >appropriate adjustment, and so on.
>> >
>> >
>> >I'll try to consolidate all path-related stuff in Files.java, so those
who
>> >care about Windows (I don't) can then have their way with the code (as
>> > long as the Unix part still works).
>> >
>> >--
>> >Dave Shields, IBM Research, shields@xxxxxxxxxxxxxx.
>>
>> Do you think that I will be able to do any further useful testing at this
>> point
>> or am I likely to get bitten by this when I move on to test merging,
saving
>> and restoring?>
>
>If I'm understanding what's happening correctly, as long as you're
consistent
>about capitalization when you use a filename, it should work fine. I would
>expect the merge test suite to work correctly on windows.
>
>I've never really understood the save/restore code (I've never looked at it
in
>detail), so I can't even guess at whether it will work or not. >>
>
>(As an interesting sidenote, Save/Restore is a great example of how hard it
is
>to really grasp what lightweight branches really *mean*. Save/Restore
>is a really neat idea, but during my one brief look through it, I realized
>that it looked a *lot* like an implementation of a branch in the
repository.
>This led me to the realization that save/restore is really doing nothing
but
>providing a private local branch in the workspace.  The only real
difference
>between s/r and a private branch is that s/r discards things to save space,
>and s/r works when you're not connected to the repository. Our tentative
plans
>are to sunset the s/r functionality and replace them with private branches
>once we have heirarchical replication working.)
>
>	-Mark

This is one of the things that attracts me to Stellation. What I would like
to be able to do is to be able to interrupt my work at any time when I
recognize an unrelated bug in the code or need to do a refactoring. I would
like to perform the bug fix or refactoring in a separate branch, possibly
off the main stream, check this in and then refresh the original branch I
was working on from the repository.

--
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email:
markcc@xxxxxxxxxxx


_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res