* State: Successfully built
* Recipe: linuxdcpp-team/linuxdcpp
* Archive: linuxdcpp-team/ppa
* Distroseries: natty
* Duration: five minutes
* Build Log: https://launchpadlibrarian.net/65941907/buildlog.txt.gz
* Upload Log:
* Builder: https://launchpad.net/builders/platinum
--
https://lau
* State: Successfully built
* Recipe: linuxdcpp-team/linuxdcpp
* Archive: linuxdcpp-team/ppa
* Distroseries: maverick
* Duration: four minutes
* Build Log: https://launchpadlibrarian.net/65941886/buildlog.txt.gz
* Upload Log:
* Builder: https://launchpad.net/builders/thallium
--
https://
* State: Successfully built
* Recipe: linuxdcpp-team/linuxdcpp
* Archive: linuxdcpp-team/ppa
* Distroseries: lucid
* Duration: four minutes
* Build Log: https://launchpadlibrarian.net/65941724/buildlog.txt.gz
* Upload Log:
* Builder: https://launchpad.net/builders/thallium
--
https://lau
Yes.
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/513027
Title:
+history since last login
Status in ADCH++:
Confirmed
Bug description:
Would be nice if I could tell the +history command n
revno: 2450
committer: Jacek Sieka
branch nick: dcplusplus
timestamp: Tue 2011-03-08 23:48:55 +0100
message:
Random header cleanup
removed:
dcpp/BitInputStream.h
dcpp/BitOutputStream.h
added:
dcpp/format.h
dcpp/typedefs.h
dwt
if the following was added:
1: when user gives no "lines" value in the history command and regged it
should send from last login , and if not regged respect default lines
setting (with offcourse a max number of lines for the "since last
loggin")
2: a option in hub settings to send always for regg
Here is a patch proposal for a full featured finished downloads log...
** Patch removed: "logdownloads2.patch"
https://bugs.launchpad.net/dcplusplus/+bug/710359/+attachment/1838720/+files/logdownloads2.patch
** Patch added: "logdownloads_f.patch"
https://bugs.launchpad.net/dcplusplus/+bug
If we want to make these choices then really not.
The proposal wasn't for fullfilling the request of the reporter, its a
compromise result of some devs' opinions in the discussion of this
report (who took time to discuss this report upon my 'daily unanswered
bug' campaign).
Again, I generally don
a 3 days interval seems really artificial and doesn't fit well in any of
the following categories:
- important update -> keep nagging to make sure the update is eventually
applied.
- unimportant update -> status bar message / unintrusive button
somewhere.
--
You received this bug notification b
Even with a severity parameter I don't there should ever be a "No show"
... what about doing a check that is users settable i.e (they can set to
check for an update every day all the way to every 7 days or something
similar)
--
You received this bug notification because you are a member of
Dcplus
I really support always showing the dialog, the above was a try to make a good
compromise between the always, sometimes, and never show (like eg. in BCDC++).
And let me remind you that because of using Coral cache by default, many users
get the upgrade reminder several days later than it was upl
the OP's proposed distinction looks great to me - one shouldn't be
forced to upgrade if the new version only improves on petty GUI features
/ docs. however, looking back through the last few years, i can't see
any version that hasn't had stability fixes as well.
the patch or the initial suggestion
im all for this
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/377693
Title:
Upgrade Dialog Should Only Be Persistent If Necessary
Status in DC++:
Confirmed
Bug description:
Recently I report
13 matches
Mail list logo
