Re: change of git-diff-tree and symlinks
- From
- Kay Sievers <kay.sievers@vrfy.org>
- Date
- May 25, 2005, 18:35 UTC
- Message-ID
- <20050525183546.GA4241@vrfy.org>
- In-Reply-To
- <Pine.LNX.4.58.0505251054110.2307@ppc970.osdl.org>
On Wed, May 25, 2005 at 11:08:54AM -0700, Linus Torvalds wrote:
Show 23 quoted lines
> > > On Wed, 25 May 2005, Kay Sievers wrote: > > > > I'm catching up with gitweb.cgi to parse the changed output. Works fine > > so far and is really much easier to parse. Here is something that does > > not work anymore. See the difference between: > > > > http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=commit;h=49cedafaf893bfe348eb7598227f1a11ae24bfd6 > > http://ehlo.org/~kay/gitweb.cgi?p=linux/hotplug/udev.git;a=commit;h=49cedafaf893bfe348eb7598227f1a11ae24bfd6 > > Yes, the new diff-tree thing doesn't show symlinks. > > The problem seems to be that we just don't have a "status" flag for it. I > think we should call it "T" for "Type change" or something, but in the > meantime let's just have the rule that instead of ignoring unknown state > changes, we always print them out as "?" instead. > > Ie something like this.. > > (And I'd suggest you make gitweb flexible enough that it does something > sane if it sees an unknown reason code - let's see what Junio thinks about > what status code we should use for this).
Ok, works again. Any reason not to mark it as 'M'? It's easyly to distinguish between a content change and a mode change by looking if the sha has changed.
Kay