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

Bug#599410: marked as done (unblock: gobby-infinote/0.4.93-2)



Your message dated Thu, 7 Oct 2010 15:12:46 +0200
with message-id <20101007131246.GZ2854@radis.liafa.jussieu.fr>
and subject line Re: Bug#599410: unblock: gobby-infinote/0.4.93-2
has caused the Debian Bug report #599410,
regarding unblock: gobby-infinote/0.4.93-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
599410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599410
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception

Please unblock package gobby-infinote

 gobby-infinote (0.4.93-2) unstable; urgency=low
 .
   * Apply upstream commit ecfdae11289287fec91513ba406f03d044dc56d9:
     Add a "Disconnect from Server" option to the context menu (#542)
   * Apply upstream commit 7538955e44168bce99db0b896321d5e1626941b3:
     Fix save all (#519)

The first commit is a new feature, the second is a bugfix.  The both commits
can be viewed in upstream's git:

http://git.0x539.de/?p=gobby.git;a=commitdiff;h=ecfdae11289287fec91513ba406f03d044dc56d9
http://git.0x539.de/?p=gobby.git;a=commitdiff;h=7538955e44168bce99db0b896321d5e1626941b3:

Both are pretty small.

unblock gobby-infinote/0.4.93-2



--- End Message ---
--- Begin Message ---
On Thu, Oct  7, 2010 at 14:03:41 +0200, Philipp Kern wrote:

>  gobby-infinote (0.4.93-2) unstable; urgency=low

Unblocked.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: