rpms/git/devel .cvsignore, 1.63, 1.64 git.spec, 1.70, 1.71 sources, 1.63, 1.64
Josh Boyer
jwboyer at gmail.com
Sat Aug 30 13:07:22 UTC 2008
- Previous message (by thread): rpms/git/devel .cvsignore, 1.63, 1.64 git.spec, 1.70, 1.71 sources, 1.63, 1.64
- Next message (by thread): rpms/git/devel .cvsignore, 1.63, 1.64 git.spec, 1.70, 1.71 sources, 1.63, 1.64
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Sat, Aug 30, 2008 at 09:06:28AM +0200, Andreas Ericsson wrote:
> Josh Boyer wrote:
>> On Fri, Aug 29, 2008 at 11:56:55AM -0400, Todd Zullinger wrote:
>>>> Though an F-9 update will not. You just don't yank out commands
>>>> like that from a stable release.
>>> Yeah, I fully agree. And that said, is there a compelling reason to
>>> push git-1.6.0 as an F9 update� (aside from "we always have to have the
>>> very latest release" mantra that many users chant)? F9 should be fine
>>> with git-1.5.6.x, shouldn't it?
>>
>> It fixes a security bug, but I think a later release of 1.5.6.x does as
>> well.
>>
>
> Also, git 1.6 moves all the git-<commands> away from /usr/bin. Judging by
> the reactions on the git mailing list from people who install from sources,
> you'd be better off shipping 1.6.0 with F10 and stick with 1.5.6.x for F9.
Um. Perhaps you should read the whole email thread you're replying to
before you reply.
josh
- Previous message (by thread): rpms/git/devel .cvsignore, 1.63, 1.64 git.spec, 1.70, 1.71 sources, 1.63, 1.64
- Next message (by thread): rpms/git/devel .cvsignore, 1.63, 1.64 git.spec, 1.70, 1.71 sources, 1.63, 1.64
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the fedora-devel-list
mailing list