git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Jochen Roemling <jochen@roemling.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: change of git-diff-tree and symlinks
Date: Sun, 29 May 2005 23:32:06 +0200	[thread overview]
Message-ID: <20050529213206.GR1036@pasky.ji.cz> (raw)
In-Reply-To: <20050529150656.GA27127@vrfy.org>

Dear diary, on Sun, May 29, 2005 at 05:06:56PM CEST, I got a letter
where Kay Sievers <kay.sievers@vrfy.org> told me that...
> On Sun, May 29, 2005 at 04:16:53PM +0200, Jochen Roemling wrote:
> > I'm planning to use cogito/git for tracking development of my (PHP 
> > based) website. Although this is the first time in my life I'm using 
> > something that smells like a SCM, it seems to work great. The only thing 
> > lacking is a working gitweb installation.
> > I downloaded the gitweb.cgi script from 
> > kernel.org/pub/software/scm/gitweb, but it dates already May 23rd.
> > 
> > In your mail below from May 25 you state that there have been quite some 
> > changes to git-diff-tree:
> > 
> > Kay Sievers wrote:
> > >
> > >The new one shows simply nothing.
> > >Shouldn't it print the mode changes like the old one?
> > >
> > and that might be the reason why I'm getting "nothing" when I'm clicking 
> > on a "commitdiff" link.
> 
> The kernel.org servers use Cogito which needs a new release. So the
> version on kernel.org is always a working version with the current
> release of Cogito as long as we don't get a git-core to provide the
> binaries.

Tomorrow evening. I'd even do it now but I feel the changes need a bit
of testing yet.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

      parent reply	other threads:[~2005-05-29 21:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 11:17 change of git-diff-tree and symlinks Kay Sievers
2005-05-25 18:08 ` Linus Torvalds
2005-05-25 18:35   ` Kay Sievers
2005-05-25 19:40     ` Junio C Hamano
2005-05-25 22:06       ` [PATCH] Adjust show-files test for dotfiles Junio C Hamano
2005-05-25 22:07       ` [PATCH] Fix type-change handling when assigning the status code to filepairs Junio C Hamano
2005-05-25 22:26       ` change of git-diff-tree and symlinks Kay Sievers
2005-05-25 22:43         ` Junio C Hamano
2005-05-25 22:47         ` Linus Torvalds
2005-05-25 23:00           ` [PATCH] Mode only changes from diff Junio C Hamano
2005-05-26  2:11             ` [PATCH] Test case portability fix Junio C Hamano
2005-05-26  2:36               ` Linus Torvalds
2005-05-26  2:55                 ` Junio C Hamano
2005-05-29 14:16 ` change of git-diff-tree and symlinks Jochen Roemling
2005-05-29 15:06   ` Kay Sievers
2005-05-29 16:06     ` Jochen Roemling
2005-05-29 16:14       ` Sebastian Kuzminsky
2005-05-30  3:17       ` Sebastian Kuzminsky
2005-05-29 18:55     ` Junio C Hamano
2005-05-29 21:32     ` Petr Baudis [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=20050529213206.GR1036@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=jochen@roemling.net \
    --cc=kay.sievers@vrfy.org \
    /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).