Summary: | git-r3 doesn't consistently work with stable git (dev-vcs/git-1.8.1.5) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Julian Ospald <hasufell> |
Component: | Eclasses | Assignee: | Michał Górny <mgorny> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=487022 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Julian Ospald
2013-10-05 15:58:59 UTC
(In reply to Julian Ospald (hasufell) from comment #0) > stable git (dev-vcs/git-1.8.1.5) doesn't know about "--unshallow" > > maybe test your eclasses before you commit them? I suggest that you change your tone. Ebuilds that use git* eclasses can't go stable for obvious reasons. Considering that 1.8.3.2 is around for two months already, I suspect that it can go stable any time soon. That said, I don't see a real reason to support the current stable in the eclass. (In reply to Michał Górny from comment #1) > That said, I don't see a real reason to support > the current stable in the eclass. So the regression is a feature? (In reply to Julian Ospald (hasufell) from comment #2) > (In reply to Michał Górny from comment #1) > > That said, I don't see a real reason to support > > the current stable in the eclass. > > So the regression is a feature? Raising required version is not a regression. |