git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Frank Li" <lznuaa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Announce: TortoiseGit 0.1 preview version
Date: Wed, 7 Jan 2009 00:05:32 +0100	[thread overview]
Message-ID: <200901070005.32730.jnareb@gmail.com> (raw)
In-Reply-To: <1976ea660901060645r641d73e6ob4e03747f1860b6a@mail.gmail.com>

On Tue, 6 Jan 2009, Frank Li wrote:

> TortoiseGit 0.2 released.

Nice. Thanks a lot for your work.

> Can you help update Git Wiki page?

Well, my stupid ISP blocks git.or.cz (and gimp.org), supposedly in
malformed attempt to reduce SPAM using MAPS (Mail Abuse Prevention
System; SPAM backwards) lists and null routing. So I have to use
proxy to edit wiki.

> It seem anyone can update Wiki page. Is it true?

It is the nature of Wiki that anyone can edit Wiki pages. It is
recommended but not necessary to register; please do not forget
to put comment ("commit message") as well.

> 
> Summary (feature matrix)
[...]

I am not involved with GUI feature Matrix; I only added simple info
about TortoiseGit. I'm not sure who is...

> > I have added information about TortoiseGit to git wiki at

-- 
Jakub Narebski
Poland

      parent reply	other threads:[~2009-01-06 23:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13  8:33 Announce: TortoiseGit 0.1 preview version 李智
2008-12-13 14:21 ` Tim Visher
2008-12-14 12:27   ` Li Frank
2008-12-14 13:09 ` Jakub Narebski
2008-12-14 13:28   ` Sverre Rabbelier
2008-12-14 13:48     ` Li Frank
2008-12-14 17:45       ` Tim Visher
2008-12-14 13:29   ` Li Frank
2008-12-15 13:56     ` Jakub Narebski
2008-12-15 14:19       ` Li Frank
     [not found]       ` <1976ea660901060645r641d73e6ob4e03747f1860b6a@mail.gmail.com>
2009-01-06 23:05         ` Jakub Narebski [this message]

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

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

  git send-email \
    --in-reply-to=200901070005.32730.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lznuaa@gmail.com \
    /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.
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 NNTP newsgroup(s).