threads / discuss / 9383

gitbox status (for those who want to hack on it)

Subject: gitbox status (for those who want to hack on it)

## tl;dr

6 messages between Aug 4, 2007 and Aug 11, 2007.

replies: 5people: 3as markdown or json

Nguyen Thai Ngoc Duy· Aug 4, 2007, 17:40 UTC · lore

I would say it's in pretty good state now because it can run through test cases. Running tests on Windows can take about an hour so I'll put test results here so you don't have to rerun the whole thing if you want to know what part needs work. Known failed tests:

t1301-shared-repo.sh: no umask on gitbox t3200-branch.sh: "unable to move logfile" and "Not a valid object name" t3405-rebase-malformed.sh: no idea t3900-i18n-commit.sh: failed due to diff not ignore \r. I don't really care about this. t3902-quoted.sh: both gitbox and the official branch fail on this, haven't looked at it t4020-diff-external.sh: "unable to fork", diff external programs should be run under sh t4110-apply-scan.sh: bad busybox patch, no cure t4114-apply-typechange.sh: ln t5000-tar-tree.sh: needs /bin/sh. Even if /bin/sh existed, still failed for some reasons. This test passed under Wine t5300-pack-object.sh: busybox ash does not understand "read -d", any workaround? t5302-pack-index.sh: dd t5502-quickfetch.sh: git-remote is a perl script. this test itself also requires perl t6002-rev-list-bisect.sh: worked under wine but failed under xp, dunno why t7003-filter-branch.sh: git-filter-branch does not understand Windows absolute path, among others t7005-editor.sh: vi is needed t7300-clean.sh: no idea, ran fine under wine t7500-commit.sh: probably because busybox diff can't diff on non-seekable input like stdin t7501-commit.sh: failed on interactive add, no idea t8001-annotate.sh: needs perl t8002-blame.sh: needs perl t9001-send-email.sh: well git-send-email is written in perl so...

Tests were run on commit f04fbf244970358a5c9d621c99b2353aecb34a12 with arguments --no-symlinks --verbose

gitbox also grows its toolkit a bit. The complete list is:

        [, [[, ash, awk, basename, bunzip2, bzcat, cat, chmod,
        cmp, cp, cut, date, diff, dirname, echo, egrep, env, expr,
        false, fgrep, find, grep, gunzip, gzip, head, ls, md5sum,
        mkdir, mv, od, patch, printenv, printf, pwd, realpath,
        rm, rmdir, sed, seq, sh, sleep, sort, sum, tail, tar,
        test, touch, tr, true, uniq, unzip, wc, which, yes, zcat

patch is not really good. ls is a hacked version, made for tests only. tar does not support verbose mode. diff does not support non-seekable input. The rest should work fine.

-- 
Duy

Johannes Schindelin· Aug 5, 2007, 15:37 UTC · re: Nguyen Thai Ngoc Duy · lore

Re: gitbox status (for those who want to hack on it)

Hi,

On Sat, 4 Aug 2007, Nguyen Thai Ngoc Duy wrote:

> I would say it's in pretty good state now because it can run through
> test cases. Running tests on Windows can take about an hour so I'll
> put test results here so you don't have to rerun the whole thing if
> you want to know what part needs work.

I think your project is awesome. Unfortunately, I did not have time to check it out yet -- work-tree regressions and msysgit keep me occupied, along with daytime job...

It should be relatively easy to get this as an option into the msysGit net installer, once /git is a submodule there.

Ciao, Dscho

Nguyen Thai Ngoc Duy· Aug 6, 2007, 01:41 UTC · re: Johannes Schindelin · lore

Re: gitbox status (for those who want to hack on it)

On 8/5/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 12 quoted lines

> Hi,
>
> On Sat, 4 Aug 2007, Nguyen Thai Ngoc Duy wrote:
>
> > I would say it's in pretty good state now because it can run through
> > test cases. Running tests on Windows can take about an hour so I'll
> > put test results here so you don't have to rerun the whole thing if
> > you want to know what part needs work.
>
> I think your project is awesome.  Unfortunately, I did not have time to
> check it out yet -- work-tree regressions and msysgit keep me occupied,
> along with daytime job...

Hey no worries. msysgit is actually good job. BTW, where was msysgit.git going? I recall I saw something there in repo.or.cz, now it's gone.

-- 
Duy

Johannes Schindelin· Aug 6, 2007, 02:24 UTC · re: Nguyen Thai Ngoc Duy · lore

Re: gitbox status (for those who want to hack on it)

Hi,

On Sun, 5 Aug 2007, Nguyen Thai Ngoc Duy wrote:

Show 15 quoted lines

> On 8/5/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > Hi,
> >
> > On Sat, 4 Aug 2007, Nguyen Thai Ngoc Duy wrote:
> >
> > > I would say it's in pretty good state now because it can run through
> > > test cases. Running tests on Windows can take about an hour so I'll
> > > put test results here so you don't have to rerun the whole thing if
> > > you want to know what part needs work.
> >
> > I think your project is awesome.  Unfortunately, I did not have time to
> > check it out yet -- work-tree regressions and msysgit keep me occupied,
> > along with daytime job...
> 
> Hey no worries. msysgit is actually good job.

Gee thanks!

> BTW, where was msysgit.git going? I recall I saw something there in 
> repo.or.cz, now it's gone.

No, it's still there: http://repo.or.cz/w/msysgit.git

What you probably saw (for a while) was my unsuccessful attempt to make this a fork of mingw.git, which is a fork of git.git.

Ciao, Dscho

Govind Salinas· Aug 11, 2007, 21:58 UTC · re: Johannes Schindelin · lore

Re: gitbox status (for those who want to hack on it)

Hi,

I'm interested in the various git on Windows projects. I can't seem to find any information on gitbox on the web though. Can you tell me a bit about it? What makes it different from the other cygwin git or mingw?

On 8/5/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 38 quoted lines

> Hi,
>
> On Sun, 5 Aug 2007, Nguyen Thai Ngoc Duy wrote:
>
> > On 8/5/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > Hi,
> > >
> > > On Sat, 4 Aug 2007, Nguyen Thai Ngoc Duy wrote:
> > >
> > > > I would say it's in pretty good state now because it can run through
> > > > test cases. Running tests on Windows can take about an hour so I'll
> > > > put test results here so you don't have to rerun the whole thing if
> > > > you want to know what part needs work.
> > >
> > > I think your project is awesome.  Unfortunately, I did not have time to
> > > check it out yet -- work-tree regressions and msysgit keep me occupied,
> > > along with daytime job...
> >
> > Hey no worries. msysgit is actually good job.
>
> Gee thanks!
>
> > BTW, where was msysgit.git going? I recall I saw something there in
> > repo.or.cz, now it's gone.
>
> No, it's still there: http://repo.or.cz/w/msysgit.git
>
> What you probably saw (for a while) was my unsuccessful attempt to make
> this a fork of mingw.git, which is a fork of git.git.
>
> Ciao,
> Dscho
>
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Nguyen Thai Ngoc Duy· Aug 11, 2007, 23:37 UTC · re: Govind Salinas · lore

Re: gitbox status (for those who want to hack on it)

On 8/11/07, Govind Salinas <govindsalinas@gmail.com> wrote:

Show 6 quoted lines

> Hi,
>
> I'm interested in the various git on Windows projects.  I can't seem
> to find any information on gitbox on the web though.  Can you tell me
> a bit about it?  What makes it different from the other cygwin git or
> mingw?

>From user point of view, it's basically mingw git without msys

requirement. You still need msys to be able to compile git though. From developer point of view, it's mingw git with a couple of unix tools ripped from busybox.

-- 
Duy