[SciPy-Dev] git on windows (was: scipy.stats)
Tue Jun 1 23:02:20 CDT 2010
On Tue, Jun 1, 2010 at 9:56 PM, <email@example.com> wrote:
> On Tue, Jun 1, 2010 at 11:39 PM, Matthew Brett <firstname.lastname@example.org> wrote:
>> On Tue, Jun 1, 2010 at 8:07 PM, <email@example.com> wrote:
>>> On Tue, Jun 1, 2010 at 6:11 PM, Fernando Perez <firstname.lastname@example.org> wrote:
>>>> Hi Josef,
>>>> On Tue, Jun 1, 2010 at 1:31 PM, <email@example.com> wrote:
>>>>> My main problem with git was the treatment of the file system, and I
>>>>> find it much easier to work with separate branches as in bzr or
>>>> One thing I've found very useful after transitioning to git for
>>>> IPython is the git new-workdir command:
>>>> It lets me keep a few branches around that I want 'permanent' on my
>>>> filesystem, in a bzr shared-repo style, while using git for the
>>>> lightweight feature-only branches. This is how it looks like right
>>>> now on my system:
>>> thanks very useful information , git-new-workdir seems to be what I would like.
>>> Does it work on Windows?
>> Sadly - probably not without a little hacking...
>> But, if you think you need it, the script is so short that it would
>> only take a short time to port to python (it's in sh):
>> I see there are symbolic links there, that will require a little fancy
>> footwork on windows, as you know.
>> If I have time I'll give it a go.
> I don't think that's necessary (symlinks sound tricky) and scipy will
> be on a public repository, so your multiple (if I understand
> correctly) clone solution will work.
Could you not use hg to do what you want (work with local directories)
and the use hg-git when you need to?
I am kinda partial to hg and bzr.
>> See you,
>> SciPy-Dev mailing list
> SciPy-Dev mailing list
More information about the SciPy-Dev