threads / discuss / 43280

Using sha1 of commit for id of gitweb Atom feed entry

Subject: Using sha1 of commit for id of gitweb Atom feed entry

## tl;dr

One message between Dec 3, 2006 and Dec 3, 2006.

replies: 0people: 1as markdown or json

Jakub Narebski· Dec 3, 2006, 23:48 UTC · lore

To all using Atom version of gitweb feeds: perhaps instead of using appropriate "commit" view gitweb URL as if of gitweb Atom feed entry, use sha1 of commit? We could create a new (unofficial for now) scheme:

  git:<sha1 of a commit>
or we can try to use tag URI scheme
 * "How to make a good ID in Atom"
   http://diveintomark.org/archives/2004/05/28/howto-atom-id
 * "Tag URI"
   http://www.taguri.org/
 * RFC 4151 - The 'tag' URI Scheme
With tag URI we need:
 1.) Identity by domain name or email address. We can use 
     (can we, Pasky?) use git.or.cz domain, or git@vger.kernel.org
     email address
 2.) Pick a date. We can use here epoch start date of 1970,
     date of 1.0 git release of 2005-12-21, or date of creating git
     mailing list of 2005, 2005-04 or 2005-04-10.
So for example the id for an entry which currently has id of
  http://repo.or.cz/w/git.git?a=commit;h=278fcd7debf19c1efee18b32f8867becb18d1a22
would have either
  git:278fcd7debf19c1efee18b32f8867becb18d1a22
or (one of the choices)
  tag:git@vger.kernel.org,2005:278fcd7debf19c1efee18b32f8867becb18d1a22
What do you think about it?
P.S. Or we could register URN... ;-)
-- 
Jakub Narebski

← back to recent threads