Re: Over-enthusiastic "unsupported packages"

Just to put my 0.02, most of my packages are marked as unmaintained, even tho' there are no standing bugs. Also there were some PHP5 QA pseudo-bugs, because these were PHP 4 packages. I am sure it was all meant well, but if something has not bugs for years, what is the criteria of unmaintainability? I understand for packages with unresolved bugs. I'd rather mark those "ancient" or "deprecated" or "to old to be used now", which is different from unmaintained. Because these are old packages, the saner thing would be not to make them PHP 5 compliant, but create new ones that replace them and are PHP 5 clean (which is something I've been doing for some on my local repo). It is just a minor annoyance for an old fart :-) -- Jesus M. Castagnetto <jesus@castagnetto.com> Web: http://www.castagnetto.com/ On Tue, Mar 13, 2012 at 15:57, till <till@php.net> wrote: > On Tue, Mar 13, 2012 at 8:14 PM, John Stokes <jstokes@heartofthefyre.us> > wrote: > > > > > > I recently transitioned on to Git, and a couple I found useful are: > > > > > > The Git Community book: > > http://book.git-scm.com/ > > > > Pro > > Git: > > http://progit.org/book/ > > I think these two work as well. > > I personally like http://gitref.org/ > > If you happen to be on a mac, I know a lot of people who got started > with the github app or gittower: > > http://mac.github.com/ (free) > http://git-tower.com/ (commercial) > > I prefer to the cli though. > > In $HOME, my .gitconfig: > > --- > [user] > name = yourname > email = you@php.net > [core] > editor = vim > [alias] > pu = !"git fetch origin -v; git fetch upstream -v; git merge > upstream/master" > pg = !"git log --pretty=format:'%h : %s' --date-order --graph" > --- > > pu = pull upstream – assumes you have an upstream remote. Pretty neat > for pull requests and stuff. > pg = pretty graph > > I don't know – besides: > > git commit > git push > git pull > > I recommend making heavy use of 'git add -p' which allows you to stage > parts of a file before you commit. Helpful especially if you change > multiple things in a file and want to split it up for individual > commits. E.g. one is CS clean-ups and the other is a new feature. > Helps to avoid monster-commits. > > Cheers, > Till > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >