Hi all,
I personally would like to keep track of the changes that happen in most of the osmocom git repositories. Generally there are currently two ways to do that.
a) The atom feed that cgit offers, e.g. http://cgit.osmocom.org/cgit/osmocom-bb/atom/?h=jolly/testing cgit does not offer this feature in a way firefox would recognize, but it works. Atom feeds are quite convenient, but in the way this works ATM one has to opt-in explicitly to every branch one wants to "follow". Newly created branches are not advertised, ...
b) The commitlog ML, which does not have any of the drawbacks of the cgit atom feed, but does not show the actual patch, in case there is one, only the revision hash.
There are several thinkable ways to bring together the best of both systems, IMHO the easiest thing to do is modify the way the commitlog ML composes its emails. The example post-receive-email scripts of git (1.7.8rc1) contains the following comment:
# hooks.showrev # The shell command used to format each revision in the email, with # "%s" replaced with the commit id. Defaults to "git rev-list -1 # --pretty %s", displaying the commit id, author, date and log # message. To list full patches separated by a blank line, you # could set this to "git show -C %s; echo". # To list a gitweb/cgit URL *and* a full patch for each change set, # use this: # "t=%s; printf 'http://.../?id=%%s' $t; echo;echo; git show -C # $t; echo" # Be careful if "..." contains things that will be expanded by shell # "eval" # or printf.
The whole file is attached. As stated on IRC, I think pasting the patches in the emails would be most convenient, must takes up quite some space in mailboxes over time. Of course that problem would be addressable with rm and there is gmane/tin, ... In any case, an added cgit link does not harm and also provides an easy way to read the patches.
Any comments and ideas how to do a similar RSS/atom feed welcome!
Kind regards -Alex
On Sat, Nov 12, 2011 at 10:41:11AM +0100, Alexander Huemer wrote:
In any case, an added cgit link does not harm and also provides an easy way to read the patches.
I've now chosen that option, you can see the result at http://lists.osmocom.org/pipermail/osmocom-commitlog/2011-November/001755.ht...
(I've already fixed the subject from projectdesc to projectname again..)
On Sat, Nov 12, 2011 at 12:00:10PM +0100, Harald Welte wrote:
On Sat, Nov 12, 2011 at 10:41:11AM +0100, Alexander Huemer wrote:
In any case, an added cgit link does not harm and also provides an easy way to read the patches.
I've now chosen that option, you can see the result at http://lists.osmocom.org/pipermail/osmocom-commitlog/2011-November/001755.ht...
(I've already fixed the subject from projectdesc to projectname again..)
cool, thx.
On Sat, Nov 12, 2011 at 12:00:10PM +0100, Harald Welte wrote:
(I've already fixed the subject from projectdesc to projectname again..)
I am not sure whether I get you correctly. Before the twiddling, the email subject always started with xxx.git, e.g. libosmocore.git. Now the situation changed, commit emails for e.g. erlang/mgw_nat.git starts with "Erlang MediaGateWay (MGW) NAT/Masquerading" while the description cgit shows is "Erlang MGW NAT/MASQ implementation" in the cloned repository, .git/description contains "Unnamed repository; edit this file 'description' to name the repository." The non-erlang repos that caused an email since the twiddling have a subject that start with "branch xxx/yyy updated" or something, so the string that contain the description in the erlang case seems to be empty. Please look at the hook script again, there is something wrong. By the way, for me xxx.git in the subject was fine.
Kind regards, -Alex
-
Alexander Huemer -
Harald Welte