login
Header Space

 
 

Mailing list archives

Search results

Found 10 matching messages (0.161 seconds). Page 1 of 1.

Re: name-rev does not show the shortest path

... It does execute that code, just not for the rev in ... actual ref, but instead gets re-written as a string when ... index 61eba34..c003e20 100644 --- a/builtin-name-rev.c +++ b/builtin ... 0, deref); + name_rev(commit, xstrdup(path), 0, 0, deref, 0); } return ...

git - Jeff King - Aug 26 2007 - 05:23

Re: name-rev does not show the shortest path

... other than > > the last. > > You're right. I misremembered name-rev to use ... this is not really good (having a fifo): -- snip -- builtin-name-rev.c ... , 0, deref); + name_rev(commit, xstrdup(path), 0, deref); } return 0; } +static void ...

git - Johannes Schindelin - Aug 27 2007 - 07:18

Re: name-rev does not show the shortest path

... same for two paths, but the 'tip_name' information is indicating a ... instrument the code like this: diff --git a/builtin-name-rev ... generation = generation; - } else + } else { + printf(" not as good as %s~%d ... else going on, such as the tag v2.6.22-rc1 ...

git - Jeff King - Aug 27 2007 - 05:24

Re: name-rev does not show the shortest path

... @cassiopeia:~/gsrc/linux-2.6$ git name-rev --tags $rev > =090567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22~ ... ~1^3~5 > > I don't now the underlaying algorithm, maybe it's to get ... > > Anyhow I want to know the earliest tag that includes this patch? ...

git - Julian Phillips - Aug 24 2007 - 07:55

Re: name-rev does not show the shortest path

... it runs "git > name-rev --name-only --tags" under the bonnet - so ... have > expected to always get the "closest" tag. ~1009^2~1^ ... ~5 to me ... ho hum. The usefulness of --contains is only ... with "git describe". It does not improve name-rev. I _think_ ...

git - Junio C Hamano - Aug 24 2007 - 14:33

Re: name-rev does not show the shortest path

... 3~5 >>> >>> I don't now the underlaying algorithm, maybe it's to ... git=20 name-rev --name-only --tags" under the bonnet - so not ... have expected= =20 to always get the "closest" tag. ~1009^2~1^ ... --=20 Julian --- And that's the way it is... =09=09-- ...

git - Julian Phillips - Aug 24 2007 - 11:21

Re: name-rev does not show the shortest path

... _think_ name-rev goes for shorter-to-type tags and does not ... that way. It _should_ pick the closer one with this code: ... ->generation > generation)) { However, it did not even get to that code ... quiet moment (which I will not have for at least another ...

git - Johannes Schindelin - Aug 25 2007 - 11:04

Re: name-rev does not show the shortest path

... looked into this, and did not find out why it is ... It does execute that code, just not for the rev in ... actual ref, but instead gets re-written as a string when ... to generate some obscenely long names: > > 0567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22 ...

git - Johannes Schindelin - Aug 26 2007 - 11:38

Re: name-rev does not show the shortest path

Hello Julian, Julian Phillips wrote: > On Thu, 23 Aug 2007, Uwe Kleine-K

git - Uwe - Aug 24 2007 - 08:52

Re: name-rev does not show the shortest path

... :38:22PM +0200, Johannes Schindelin wrote: > > > The old code _should_ have worked; it ... that we have effectively _thrown away_ the > "smaller numbers over larger ones" information ... other than > the last. You're right. I misremembered name-rev to use ...

git - Johannes Schindelin - Aug 27 2007 - 05:57

speck-geostationary