Le mercredi 06 mai 2009 à 08:41 +0530, Tirumurti Vasudevan a écrit :
> i have a problem.
> i saw the damned lies page that GNOME 2.28 (development) is the one
> to work with.
> when i clone a repo there is no 2.28 folder there.
Hi Tirumurti,
GNOME 2.28 is currently using the 'master' branch of
On Wed, May 6, 2009 at 6:07 AM, Matthias Clasen
wrote:
> I've just created a gnome-2-26 branch for GConf.
> I had to remove a single translation from ne.po before being able to
> do so, since msgfmt -c was complaining about it.
>
> The reason for branching is that I want to fix
> http://bugzilla.g
This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.
There have been following string additions to module 'gconf.master':
+ "Could not send message to GConf daemon: %s"
Note that this doesn't directly indicate a string freeze break, but it
might be worth in
i have a problem.
i saw the damned lies page that GNOME 2.28 (development) is the one
to work with.
when i clone a repo there is no 2.28 folder there.
nor a folder called master
where can i put the newly updated file?
thanks in advance
dr.tv
--
My blogs: [all in Tamil]
http://anmikam4dumbme.b
I've just created a gnome-2-26 branch for GConf.
I had to remove a single translation from ne.po before being able to
do so, since msgfmt -c was complaining about it.
The reason for branching is that I want to fix
http://bugzilla.gnome.org/show_bug.cgi?id=558619 which will allow the
defaults servi
On 05/05/2009 01:28 AM, Shaun McCance wrote:
This assumes that the branch is merged into master otherwise. I strongly
suggest cherry-pick instead of merge.
Isn't that going to cause merge conflicts for me the
maintainer when I try to merge from my stable branches
to master? I can pretty much
