On 02/28/11 14:36, Alaric Snell-Pym wrote:
So far, I've written my omelette recipe into SVN; and tools are
gathering in the gazette-tools egg and on the wiki page at
http://wiki.call-cc.org/gazette - hopefully this weekend I'll get a
chance to integrate and test what we have, and we may even
* Alaric Snell-Pym ala...@snell-pym.org.uk [110216 10:41]:
When a community agrees it'd be cool to do something on a regular basis,
to begin with, there's a lot of enthusiasm and volunteering, so things
go well.
However, a crucial point comes at which producing that thing starts to
become
On 02/28/11 14:10, Christian Kellermann wrote:
The Gazette is reaching that point, and I want to save it.
After all the wonderful responses to this thread and the awesome
amount of work that it has triggered. I wondered who is working on
a new issue now?
This feels like people that have
Agreed!
Excellent!
I've outlined what I think would be good; of course, partial
implementations (I did X but Y is too hard) are a step in the right
direction, and somebody else might do Y later, too :-) Every little helps!
Could you, once again, list the necessary parts and put this
Alaric Snell-Pym wrote:
On 02/16/11 15:04, Andy Bennett wrote:
This bash command, executed inside a git repo, should do the trick:
-
for b in `git branch -a --no-color | sed -e 's/^*//' -e
's/^\s*\(\S*\).*/\1/'` ; do echo * On `echo $b | sed -e
's#^remotes/##'`:; git log
Andy Bennett scripsit:
Strange! The first part of the first sed is supposed to remove the '*'
that indicates the currently checked out branch.
The meaning of the regex /^*/ is implementation-dependent: it can be
read as remove any number of hats, including zero or remove a star at
the
On Thu, Feb 17, 2011 at 10:51 PM, John Cowan co...@mercury.ccil.org wrote:
Andy Bennett scripsit:
Strange! The first part of the first sed is supposed to remove the '*'
that indicates the currently checked out branch.
The meaning of the regex /^*/ is implementation-dependent: it can be
read
Hi,
Super special bonus point:
5) Write a script that, given a date range, parses the mailing list
archive into wiki markup for a list of links to the posts in the
archive, along with links to the user's pages as per (4), grouped by thread.
The attached script will process the web-based
* Andy Bennett andy...@ashurst.eu.org [110217 17:36]:
Hi,
Super special bonus point:
5) Write a script that, given a date range, parses the mailing list
archive into wiki markup for a list of links to the posts in the
archive, along with links to the user's pages as per (4), grouped
From: Andy Bennett andy...@ashurst.eu.org
Subject: Re: [Chicken-users] Save the Gazette!
Date: Thu, 17 Feb 2011 16:32:44 +
Whoa. Thanks, Andy!
cheers,
felix
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman
BTW, perhaps we should make some room in the egg repo for this
work. If nobody objects, I can do the svn log parsing.
cheers,
felix
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix
fe...@call-with-current-continuation.org wrote:
BTW, perhaps we should make some room in the egg repo for this
work.
Maybe under the gazette dir?
If nobody objects, I can do the svn log parsing.
Great!
Best wishes.
Mario
--
From: Mario Domenech Goulart mario.goul...@gmail.com
Subject: Re: [Chicken-users] Save the Gazette!
Date: Thu, 17 Feb 2011 15:10:32 -0500
On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix
fe...@call-with-current-continuation.org wrote:
BTW, perhaps we should make some room in the egg repo
On 02/17/11 14:33, Alex Shinn wrote:
Or replace every use of sed and awk with perl, which
is consistent across all platforms and scales better.
However, as I think most of the people likely to run this code will have
chicken installed and know Scheme, why not do it in Chicken? I believe
On Thu, 17 Feb 2011 21:16:43 +0100 (CET) Felix
fe...@call-with-current-continuation.org wrote:
From: Mario Domenech Goulart mario.goul...@gmail.com
Subject: Re: [Chicken-users] Save the Gazette!
Date: Thu, 17 Feb 2011 15:10:32 -0500
On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix
fe
When a community agrees it'd be cool to do something on a regular basis,
to begin with, there's a lot of enthusiasm and volunteering, so things
go well.
However, a crucial point comes at which producing that thing starts to
become a chore, no matter how popular the product is. At this point, if
Hi Alaric,
Thanks for volunteering to write editorial content. As for your
requests, I believe that you can already do 2) by using the Trac RSS
feed:
http://bugs.call-cc.org/timeline?ticket=onchangeset=onmilestone=offwiki=offmax=50daysback=7format=rss
Obviously you can set the 'daysback'
Ivan,
I understood Alaric's message to be a request to take the commit
log, c, regardless of the form they are in, and convert that
directly into a form useable by the gazette: Summarized, formatted,
and checked in to the repository.
-Alan
On Wed, Feb 16, 2011 at 07:04:28PM +0900, Ivan Raikov
On 02/16/11 13:22, Alan Post wrote:
Ivan,
I understood Alaric's message to be a request to take the commit
log, c, regardless of the form they are in, and convert that
directly into a form useable by the gazette: Summarized, formatted,
and checked in to the repository.
Sort of. I know
From: Alaric Snell-Pym ala...@snell-pym.org.uk
Subject: Re: [Chicken-users] Save the Gazette!
Date: Wed, 16 Feb 2011 13:34:18 +
Sort of. I know there's RSS and so on available, but it currently needs
much manual work to turn it into content. I'd like a script that pulls
that RSS feed
Hi,
3) A script that, when run in a local git checkout, or maybe by talking
direct to the core git repo, lists all the commits in a specified time
period, grouped by branch.
For bonus points, the output of scripts (2) and (3) could be actual
markup for putting straight into the gazette, say
On 02/16/11 14:20, Felix wrote:
... and I want a pony. :-)
What colour?
It is never the question of whether some well-crafted, time-saving
tool is useful or not, that's obvious. It's always the question of who
does it and when. So instead of discussing the technical details, I
propose to
On 02/16/11 15:04, Andy Bennett wrote:
This bash command, executed inside a git repo, should do the trick:
-
for b in `git branch -a --no-color | sed -e 's/^*//' -e
's/^\s*\(\S*\).*/\1/'` ; do echo * On `echo $b | sed -e
's#^remotes/##'`:; git log --pretty=format:' * (%h): %s (%an,
23 matches
Mail list logo
