The bzr revision map

The bzr revision map

[Eric S. Raymond]

It is not reflected in the review7 repository, but I have just updated the
conversion machinery to check a map of bzr revisions to committer/date
stamps into /etc on each full conversion.

This will support Emacs Lisp code (not yet written) to find a bzr
revision number around point and check out the corresponding git
revision.

This data file will be in review8.  The code is on my to-do list.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

The right of the citizens to keep and bear arms has justly been considered as
the palladium of the liberties of a republic; since it offers a strong moral
check against usurpation and arbitrary power of rulers; and will generally,
even if these are successful in the first instance, enable the people to resist
and triumph over them."
        -- Supreme Court Justice Joseph Story of the John Marshall Court

Re: The bzr revision map

[Stefan Monnier]

> It is not reflected in the review7 repository, but I have just updated the
> conversion machinery to check a map of bzr revisions to committer/date
> stamps into /etc on each full conversion.

> This will support Emacs Lisp code (not yet written) to find a bzr
> revision number around point and check out the corresponding git
> revision.

Thanks for the idea, bu don't bother, please, it's not worth the effort,
nor the corresponding disk space.


        Stefan

Re: The bzr revision map

[Eric S. Raymond]

Stefan Monnier <monnier@iro.umontreal.ca>:
> > It is not reflected in the review7 repository, but I have just updated the
> > conversion machinery to check a map of bzr revisions to committer/date
> > stamps into /etc on each full conversion.
> 
> > This will support Emacs Lisp code (not yet written) to find a bzr
> > revision number around point and check out the corresponding git
> > revision.
> 
> Thanks for the idea, bu don't bother, please, it's not worth the effort,
> nor the corresponding disk space.

Oh?  I'm not attached to the idea, but I thought it was on my list of
requirements.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: The bzr revision map

[Stefan Monnier]

> Oh?  I'm not attached to the idea, but I thought it was on my list of
> requirements.

It might be good for this map to exist somewhere, but I don't think it's
useful enough to have it in Emacs's repository.


        Stefan

Re: The bzr revision map

[Eric S. Raymond]

Stefan Monnier <monnier@iro.umontreal.ca>:
> > Oh?  I'm not attached to the idea, but I thought it was on my list of
> > requirements.
> 
> It might be good for this map to exist somewhere, but I don't think it's
> useful enough to have it in Emacs's repository.

OK. Do you have a suggestion as to wher it should be archived?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: The bzr revision map

[Stefan Monnier]

> Oh?  I'm not attached to the idea, but I thought it was on my list of
> requirements.

E.g. I can't remember the last time I had to look up a revision by revno.


        Stefan

Re: The bzr revision map

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 31 Oct 2014 16:08:57 -0400
> Cc: emacs-devel@gnu.org
> 
> > Oh?  I'm not attached to the idea, but I thought it was on my list of
> > requirements.
> 
> E.g. I can't remember the last time I had to look up a revision by revno.

The bug tracker is full of them (as in "fixed in rXYZZY on the
trunk").

Re: The bzr revision map

[Stefan Monnier]

>> > Oh?  I'm not attached to the idea, but I thought it was on my list of
>> > requirements.
>> E.g. I can't remember the last time I had to look up a revision by revno.
> The bug tracker is full of them (as in "fixed in rXYZZY on the
> trunk").

Of course, I see revno used on a regular basis.  But I've very rarely
had to look them up.  And I basically never use them myself.


        Stefan

Re: The bzr revision map

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: esr@thyrsus.com,  emacs-devel@gnu.org
> Date: Fri, 31 Oct 2014 23:06:25 -0400
> 
> >> E.g. I can't remember the last time I had to look up a revision by revno.
> > The bug tracker is full of them (as in "fixed in rXYZZY on the
> > trunk").
> 
> Of course, I see revno used on a regular basis.  But I've very rarely
> had to look them up.  And I basically never use them myself.

My point is that someone who does need to look up what exactly were
the changes referenced on the bug tracker, might find the revision map
useful.  That someone doesn't have to be called Stefan Monnier,
obviously.

Re: The bzr revision map

[Angelo Graziosi]

Eli Zaretskii wrote:

>> From: Stefan Monnier
>>
>> >> E.g. I can't remember the last time I had to look up a revision by revno.
>> > The bug tracker is full of them (as in "fixed in rXYZZY on the
>> > trunk").
>>
>> Of course, I see revno used on a regular basis.  But I've very rarely
>> had to look them up.  And I basically never use them myself.
>
> My point is that someone who does need to look up what exactly were
> the changes referenced on the bug tracker, might find the revision map
> useful.  That someone doesn't have to be called Stefan Monnier,
> obviously.

Out of curiosity, how we can do a binary search without a progressive 
revision number?

In the past, just this list suggested me to do a binary search to find 
when a bug or a regression was introduced...


Thanks,
  Angelo.

Re: The bzr revision map

[Alexis]

Angelo Graziosi writes:

> Out of curiosity, how we can do a binary search without a progressive 
> revision number?
>
> In the past, just this list suggested me to do a binary search to find 
> when a bug or a regression was introduced...

https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html


Alexis.

Re: The bzr revision map

[Eli Zaretskii]

> From: Alexis <flexibeast@gmail.com>
> Date: Sat, 01 Nov 2014 21:04:12 +1100
> 
> Angelo Graziosi writes:
> 
> > Out of curiosity, how we can do a binary search without a progressive 
> > revision number?
> >
> > In the past, just this list suggested me to do a binary search to find 
> > when a bug or a regression was introduced...
> 
> https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html

Indeed, and bzr also has the bisect command, so manual binary search
is not needed.

Re: The bzr revision map

[Andreas Schwab]

Angelo Graziosi <angelo.graziosi@alice.it> writes:

> Out of curiosity, how we can do a binary search without a progressive
> revision number?
>
> In the past, just this list suggested me to do a binary search to find
> when a bug or a regression was introduced...

Just continue to do it and use git bisect.  No need for manual counting.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: The bzr revision map

[Angelo Graziosi]

Il 01/11/2014 11:10, Andreas Schwab ha scritto:
> Angelo Graziosi <angelo.graziosi@alice.it> writes:
>
>> Out of curiosity, how we can do a binary search without a progressive
>> revision number?
>>
>> In the past, just this list suggested me to do a binary search to find
>> when a bug or a regression was introduced...
>
> Just continue to do it and use git bisect.  No need for manual counting.

Oh, I didn't know about it... thanks.

Ciao,
Angelo.