# path-restricted gitk with tags showing up?

4 messages from 2006-08-01 to 2006-08-01. Participants: Olivier Galibert, Linus Torvalds, Sergey Vlasov.
Thread: https://gitlist.dev/t/5072

## Olivier Galibert, 2006-08-01 17:42

Subject: path-restricted gitk with tags showing up?
Message-ID: <20060801174210.GA81699@dspnet.fr.eu.org>
URL: https://gitlist.dev/e/20060801174210.GA81699%40dspnet.fr.eu.org

```
I'd like to do a (f.i) gitk include/sound/asound.h but still see the
commits which are in the DAG delimited by the alsa commits and have
tags attached.  The aim is to know what changes where in what released
kernel version.  Is there a way to do that?

  OG.

```

## Linus Torvalds, 2006-08-01 18:39

Subject: Re: path-restricted gitk with tags showing up?
Message-ID: <Pine.LNX.4.64.0608011137580.4168@g5.osdl.org>
URL: https://gitlist.dev/e/Pine.LNX.4.64.0608011137580.4168%40g5.osdl.org
In-Reply-To: <20060801174210.GA81699@dspnet.fr.eu.org>

```


On Tue, 1 Aug 2006, Olivier Galibert wrote:
>
> I'd like to do a (f.i) gitk include/sound/asound.h but still see the
> commits which are in the DAG delimited by the alsa commits and have
> tags attached.  The aim is to know what changes where in what released
> kernel version.  Is there a way to do that?

Not right now. It should be fairly easy to add a flag that marks all 
tagged commits (or, indeed, anything that is reachable from .git/refs/) as 
"TREECHANGE" so that they aren't optimized away, but we don't have 
anything like that right now at least.

A small exercise for somebody who wants to get into git, perhaps? Hint, 
hint..

		Linus

```

## Sergey Vlasov, 2006-08-01 19:13

Subject: Re: path-restricted gitk with tags showing up?
Message-ID: <20060801231329.82d934a2.vsu@altlinux.ru>
URL: https://gitlist.dev/e/20060801231329.82d934a2.vsu%40altlinux.ru
In-Reply-To: <20060801174210.GA81699@dspnet.fr.eu.org>

```
On Tue, 1 Aug 2006 19:42:10 +0200 Olivier Galibert wrote:

> I'd like to do a (f.i) gitk include/sound/asound.h but still see the
> commits which are in the DAG delimited by the alsa commits and have
> tags attached.  The aim is to know what changes where in what released
> kernel version.  Is there a way to do that?

Since git-1.4.0 gitk shows this information in the "Follows:" and
"Precedes:" lines for each commit (you need to enable "Display nearby
tags" in preferences).  In your case, the "Precedes" line will show the
first kernel version which included the change.

Note that loading this information takes some time; gitk tries to load
it in background, so you may see empty "Follows" and "Precedes" lines
for some time.

```

## Olivier Galibert, 2006-08-01 19:33

Subject: Re: path-restricted gitk with tags showing up?
Message-ID: <20060801193337.GA93307@dspnet.fr.eu.org>
URL: https://gitlist.dev/e/20060801193337.GA93307%40dspnet.fr.eu.org
In-Reply-To: <20060801231329.82d934a2.vsu@altlinux.ru>

```
On Tue, Aug 01, 2006 at 11:13:29PM +0400, Sergey Vlasov wrote:
> On Tue, 1 Aug 2006 19:42:10 +0200 Olivier Galibert wrote:
> 
> > I'd like to do a (f.i) gitk include/sound/asound.h but still see the
> > commits which are in the DAG delimited by the alsa commits and have
> > tags attached.  The aim is to know what changes where in what released
> > kernel version.  Is there a way to do that?
> 
> Since git-1.4.0 gitk shows this information in the "Follows:" and
> "Precedes:" lines for each commit (you need to enable "Display nearby
> tags" in preferences).  In your case, the "Precedes" line will show the
> first kernel version which included the change.
> 
> Note that loading this information takes some time; gitk tries to load
> it in background, so you may see empty "Follows" and "Precedes" lines
> for some time.

Works rather well, thanks.

  OG.

```