git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PYRITE] Status update and call for information.

From
Karl Hasselström <kha@treskal.com>
Date
May 23, 2008, 13:12 UTC
Message-ID
<20080523131228.GA4292@diana.vm.bytemark.co.uk>
In-Reply-To
<5d46db230805230536r18ac606j93a210d0b2864719@mail.gmail.com>
On 2008-05-23 07:36:25 -0500, Govind Salinas wrote:
Show 21 quoted lines
> On Fri, May 23, 2008 at 1:45 AM, Karl Hasselström <kha@treskal.com>
> wrote:
>
> > You do realize that no matter how you define your sequential
> > numbers, they can't be both globally consistent and unique? (That
> > is, either different repositories will assign different numbers to
> > the same commit, or the same number could be assigned to more than
> > one commit.)
>
> Of course, no one makes the claim that rev numbers are unique or
> even that a commit has the same revision number between branches in
> the same repository. Hg states that flat out and I believe bzr says
> the same, although I am pretty sure they determine their numbers
> some other way. I make no such claim. What I do claim is that for a
> given branch, a commit should always have the same revision number.
> Sure, If you merge a commit from another branch, it's revnum might
> change, but that is ok. As long as, assuming you have not re-written
> master, 10:master will always point to the same commit I think I am
> providing something worth while. Also, AFAIK the order of parentage
> is part of the hash that makes a commit ID, so if my master is a
> clone of your master, it should share revision numbers.

Yes, with those restrictions it can be made to work. (What confused me was that you brought up performance as the only reason to prefer hashes to your rev numbers. But hashes also have the advantage that they're immutable, whereas your rev numbers are not.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Govind SalinasNext: Jakub Narebski
Message 4 of 18 in “[PYRITE] Status update and call for information.”
  1. Govind SalinasMay 23, 2008
  2. Karl HasselströmMay 23, 2008
  3. Govind SalinasMay 23, 2008
  4. Karl HasselströmMay 23, 2008
  5. Jakub NarebskiMay 24, 2008
  6. Govind SalinasMay 24, 2008
  7. Jakub NarebskiMay 24, 2008
  8. Govind SalinasMay 24, 2008
  9. Jakub NarebskiMay 24, 2008
  10. Jan KruegerMay 25, 2008
  11. Govind SalinasMay 25, 2008
  12. Dmitry PotapovMay 24, 2008
  13. Jakub NarebskiMay 24, 2008
  14. Govind SalinasMay 24, 2008
  15. Jakub NarebskiMay 25, 2008
  16. Govind SalinasMay 25, 2008
  17. Dmitry PotapovMay 24, 2008
  18. Jakub NarebskiMay 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.