Using sha1 of commit for id of gitweb Atom feed entry

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
     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@xxxxxxxxxxxxxxx,2005:278fcd7debf19c1efee18b32f8867becb18d1a22

What do you think about it?

P.S. Or we could register URN... ;-)
-- 
Jakub Narebski
Poland
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]