git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
	git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: Git for Windows 1.6.2.1-preview20090322
Date: Mon, 23 Mar 2009 00:25:57 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0903230015020.10279@pacific.mpi-cbg.de> (raw)
In-Reply-To: <20090322225315.GC22428@sigill.intra.peff.net>

Hi,

On Sun, 22 Mar 2009, Jeff King wrote:

> On Sun, Mar 22, 2009 at 10:17:23PM +0100, Johannes Schindelin wrote:
> 
> > - Some commands are not yet supported on Windows and excluded from the 
> >   installation; namely: git archimport, git cvsexportcommit, git 
> >   cvsimport, git cvsserver, git filter-branch, git instaweb, git 
> >   send-email, git shell.
> 
> A few people have asked about filter-branch on Windows recently;

I am not aware of any.  But then, I think nobody mentioned it on the 
msysgit list (which would be the correct place), and I am likely to have 
missed it if it was sent elsewhere.

> JSixt indicated that it works from his built version:
> 
>   http://article.gmane.org/gmane.comp.version-control.git/112103
> 
> Is it time to include it?

Actually, not only Hannes' version runs the test t7003 okay, but also 
4msysgit's version.

But let's reduce the differences between git.git and 4msysgit.git further 
first.

I'll wait with the next Git for Windows release until the next official 
Git version is released, anyway.  Or if Steffen wants to take msysGit over 
again when he comes back, he will wait until the next official Git 
versions is released, anyway.

Ciao,
Dscho

  reply	other threads:[~2009-03-22 23:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-08  1:10 Git for Windows 1.6.2-preview20090308 Johannes Schindelin
2009-03-08  2:07 ` Sverre Rabbelier
2009-03-08 11:13 ` Alexander Gavrilov
2009-03-08 11:54   ` Johannes Schindelin
2009-03-08 12:59 ` Lee Henson
2009-03-08 13:26 ` Jakub Narebski
2009-03-08 18:43   ` Johannes Schindelin
2009-03-08 21:30 ` Christian MICHON
2009-03-08 21:36   ` [msysGit] " Janos Laube
2009-03-08 21:39     ` Christian MICHON
2009-03-09 10:34 ` Rutger Nijlunsing
2009-03-09 10:37   ` Johannes Schindelin
2009-03-22 21:17 ` Git for Windows 1.6.2.1-preview20090322 Johannes Schindelin
2009-03-22 22:53   ` Jeff King
2009-03-22 23:25     ` Johannes Schindelin [this message]
2009-03-23  2:53       ` Jeff King
2009-03-23 10:59         ` Johannes Schindelin
2009-03-23 22:03   ` Ludvig Strigeus
2009-03-23 23:07     ` Rostislav Svoboda
2009-03-24  2:06     ` Johannes Schindelin
2009-03-24  1:35   ` Markus Heidelberg
2009-03-24  2:04     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.00.0903230015020.10279@pacific.mpi-cbg.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=msysgit@googlegroups.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).