On Tue, 2009-04-21 at 23:13 +0200, Garrett LeSage wrote:
In fact, you probably should have a file which would be updated as
developers churn along (distributing the effort over time), where each
big notable feature/bugfix/etc. is recorded as a line in the file
whenever it officially lands.
On Wed, 2009-04-22 at 09:36 +0100, Scott James Remnant wrote:
On Tue, 2009-04-21 at 23:13 +0200, Garrett LeSage wrote:
In fact, you probably should have a file which would be updated as
developers churn along (distributing the effort over time), where each
big notable
I'm new to this (having just joined the gnome-shell-list, but I quite
like this suggestion, with one possible addition. I was wondering
whether all of them could be on a circular strip (think zoetrope
http://en.wikipedia.org/wiki/Zoetrope) which could easily be rotated so
that you can choose and
El dt 21 de 04 de 2009 a les 09:11 -0300, en/na Jonh Wendell va
escriure:
Branch names are gnome-2-26.
Development will happen in master.
Cheers,
l10n.gnome.org updated!
Cheers,
--
gil forcada
[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free
Hello.
With all the buzz around GNOME 3, I think it would be useful to define
a default desktop widget application/library for GNOME.
I do only know gdesklets and screenlets, maybe these projects could be
unified around some kind of default widget library, so people who want
to develop widgets
Hey,
The GTK+ team documented how they'd like to see the git commit messages
in http://git.gnome.org/cgit/gtk+/tree/README.commits
= copy paste =
The expected format for git commit messages is as follows:
=== begin example commit ===
Short explanation
On Wed, Apr 22, 2009 at 7:46 AM, Vincent Untz vu...@gnome.org wrote:
Hey,
The GTK+ team documented how they'd like to see the git commit messages
in http://git.gnome.org/cgit/gtk+/tree/README.commits
= copy paste =
The expected format for git commit
Le samedi 18 avril 2009, à 21:54 -0400, Behdad Esfahbod a écrit :
Hey,
I first wrote Makefile.am magic for Pango to generate ChangeLog from git
on demand. Those macros have been modified and gathered in
http://live.gnome.org/Git/ChangeLog to only generate ChangeLog for make
dist. I
On Wed, 2009-04-22 at 16:47 +0200, Vincent Untz wrote:
Le samedi 18 avril 2009, à 21:54 -0400, Behdad Esfahbod a écrit :
Hey,
I first wrote Makefile.am magic for Pango to generate ChangeLog from git
on demand. Those macros have been modified and gathered in
Le mercredi 22 avril 2009, à 15:56 +0100, Bastien Nocera a écrit :
On Wed, 2009-04-22 at 16:47 +0200, Vincent Untz wrote:
Le samedi 18 avril 2009, à 21:54 -0400, Behdad Esfahbod a écrit :
Hey,
I first wrote Makefile.am magic for Pango to generate ChangeLog from git
on demand.
On Wed, Apr 22, 2009 at 4:09 PM, Christophe Fergeau t...@gnome.org wrote:
Hi Vincent,
2009/4/22 Vincent Untz vu...@gnome.org
- When committing code on behalf of others use the --author option, e.g.
git commit -a --author Joe Coder j...@coder.org and --signoff.
Le vendredi 17 avril 2009, à 21:51 -0400, Behdad Esfahbod a écrit :
Hi,
Based on an idea from halfline, I hacked a few lines to automatically
generate .gitignore from Makefile.am. It grew to a couple hundred lines,
and is available from pango/git.mk.
[...]
Bug reports, enhancements, etc
Vincent Untz wrote:
Frédéric (fredp) is suggesting to also propose a standard scheme to
reference bugs that are fixed by a commit (so we can script things if
it's needed one day -- that's similar to what Debian does).
Something like Closes: #123456 or Fixes: #123456.
I think KDE uses
Le mercredi 22 avril 2009, à 16:46 +0200, Vincent Untz a écrit :
Hey,
The GTK+ team documented how they'd like to see the git commit messages
in http://git.gnome.org/cgit/gtk+/tree/README.commits
= copy paste =
The expected format for git commit
Hi Vincent,
2009/4/22 Vincent Untz vu...@gnome.org
- When committing code on behalf of others use the --author option, e.g.
git commit -a --author Joe Coder j...@coder.org and --signoff.
Opinions?
Not sure about the --signoff
Evolution isn't yet ready to do anything. I heard there are similar
modules. Settling with jhbuild w/git, and the entire clone, pro'lly
gonna eat lot of time. If its possible, I second this.
-Srini.
On Wed, 2009-04-22 at 10:50 -0500, Jason D. Clinton wrote:
With the outstanding git migration
On Wed, Apr 22, 2009 at 5:01 PM, Srinivasa Ragavan sraga...@novell.com wrote:
Evolution isn't yet ready to do anything. I heard there are similar
modules. Settling with jhbuild w/git, and the entire clone, pro'lly
gonna eat lot of time. If its possible, I second this.
-Srini.
On Wed,
On 04/22/2009 11:15 AM, Vincent Untz wrote:
Le vendredi 17 avril 2009, à 21:51 -0400, Behdad Esfahbod a écrit :
Hi,
Based on an idea from halfline, I hacked a few lines to automatically
generate .gitignore from Makefile.am. It grew to a couple hundred lines,
and is available from
Hi,
GNOME Media 2.26.x has been branched in gnome-2-26 branch.
Development will continue in master branch.
regards,
--
Marc-André Lureau
Sent from Helsinki, Southern Finland, Finland
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
On 04/22/2009 10:46 AM, Vincent Untz wrote:
I'd like to suggest that this is the default recommendation for GNOME
modules, since having some common guidelines will make the life easier
for most people. If some maintainers disagree, they can of course ask
for something else in their modules.
On Wed, Apr 22, 2009 at 11:50 AM, Jason D. Clinton m...@jasonclinton.com
wrote:
With the outstanding git migration problems (and the resulting
inability to jhbuild) perhaps we should postpone 2.27.1 by one week?
Do we have a list of modules that still have trouble after the git migration ?
Am Mittwoch, den 22.04.2009, 15:20 -0400 schrieb Matthias Clasen:
Do we have a list of modules that still have trouble after the git migration ?
http://mail.gnome.org/archives/gnome-infrastructure/2009-April/msg00165.html
krh gnomemm and seahorse are in place now
krh but additionally there was a
22 matches
Mail list logo
