[Bug 319096] Re: Please upgrade git-core to 1.6.2
Debdiff for karmic, when you get around to it. ** Attachment added: "git-core_1.6.2.4-1ubuntu1.debdiff" http://launchpadlibrarian.net/26118904/git-core_1.6.2.4-1ubuntu1.debdiff ** Summary changed: - Please upgrade git-core to 1.6.2 + Please upgrade git-core to 1.6.2.4 ** Description changed: - Please upgrade git-core 1.6.0.4 to git-core 1.6.2 found in debian. + Please upgrade git-core 1.6.0.4 to git-core 1.6.2.4 found in debian. -- Please upgrade git-core to 1.6.2.4 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319096] Re: Please upgrade git-core to 1.6.2
Doesn’t the Debian Import Freeze only affect automatic syncs from Debian? This package is ineligible for an automatic sync anyway, because of the Ubuntu modification. That is why it was held back on the obsolete version for so long. So perhaps this would be less of a problem in the future if we could find some way to remove the Ubuntu modification; for example, can we move cvsps to main? -- Please upgrade git-core to 1.6.2 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 319096] Re: Please upgrade git-core to 1.6.2
On Thu, 2009-03-12 at 16:35 +, Joseph Smidt wrote: > I admit my last post was a knee-jerk reaction to a perceived neglect of > git do to a personal bias. I am sorry I handled the situation so > immaturely. > No problem ;) We all have a scream and shout sometimes, often on our blogs I'm obviously not biased against GIT in any way that'd stop me wanting to import it - I actually /use/ it daily, which is why I rant about it sometimes. A correction to your post though, Jan 19 is before FF, but after Debian Import Freeze (Dec 25th) so this request was already after the relevant freeze. I assigned the bug to myself as part of the usual sponsorship process, we don't like them to go unassigned. As you'd expect, this isn't the only bug on my list - nor the only project. I'm sorry that I didn't get to it, but it does all come down to a matter of priority. Had the update fixed some high or critical bugs, it would have been much higher on my list and more likely to have been done. I hear your concerns about the un-filfilled confirmed bug reports. Unfortunately there doesn't seem to be any quick solution to this problem that Ubuntu is having. The simple fact is that we have literally hundreds of thousands of bugs, and less than a hundred developers. For example, it took two of us almost a week to fully debug and iron out the issue of the floppy disk drive not being auto-loaded. That bug had sat confirmed for two releases! Scott -- Scott James Remnant sc...@canonical.com -- Please upgrade git-core to 1.6.2 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319096] Re: Please upgrade git-core to 1.6.2
Scott, I admit my last post was a knee-jerk reaction to a perceived neglect of git do to a personal bias. I am sorry I handled the situation so immaturely. -- Please upgrade git-core to 1.6.2 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319096] Re: Please upgrade git-core to 1.6.2
Scott, On Jan. 19, well before the feature freeze, a bug report was filed to bring git 1.6.0.4 to 1.6.0.6 to fix bugs and the patch to do so was even provided. You had some initial issues with the patch, but after they were addressed you assigned yourself to the bug report on Jan. 20. Then you decided to wait until after the feature freeze to say "None of these bugs seem severe enough to warrant breaking... Feature Freeze". Scott, is it standard practice for member's of Ubuntu's technical board to assign themselves to bugs with patches submitted over a month before the feature freeze then wait until after the feature freeze and say "sorry, can't fix bugs after the feature freeze." Perhaps this is why Ubuntu has so many un-fulfilled confirmed bug reports. Please: 1. Don't assign yourself to bugs of packages you have a public disdain for [1] if you won't patch them. 2. Don't assign yourself to bugs with a patch, then wait until after feature freeze to say "sorry, it's now too late." PS. To be fair, most other Ubuntu developers do upload your patches when you get patches into the form they request when submitted a month before the feature freeze. [1] http://www.netsplit.com/2009/02/17/git-sucks/ -- Please upgrade git-core to 1.6.2 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319096] Re: Please upgrade git-core to 1.6.2
None of these bugs seem severe enough to warrant breaking both Upstream Version Freeze and Feature Freeze for this, we can pick the update up in karmic -- Please upgrade git-core to 1.6.2 https://bugs.launchpad.net/bugs/319096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
