Sixers Reach Buyout Deal With Danny Granger

10:38pm: Granger’s representatives were present at the Clippers/Rockets game to meet with Los Angeles officials, per Shelburne (Twitter link). Shelburne adds that the Rockets’ push to sign Granger could have something to do with the appearance.

5:05pm: Stein and colleague Ramona Shelburne suggest in their full story that the Clippers are the favorites, and add that Granger is seeking a championship contender as well as playing time.

4:09pm: The Sixers and Danny Granger have reached agreement on a buyout, the team has announced, and Philadelphia has placed the 30-year-old on waivers. David Aldridge of first reported the news. The Clippers have emerged as front runners for Granger, writes Adrian Wojnarowski of Yahoo! Sports. Aldridge names the Clippers, Rockets, Bulls, Heat and Spurs as Granger’s preferred destinations, reiterating his report from earlier today. Marc Stein of casts it as a battle between the Clippers and the Spurs (Twitter link).

“Given Danny’s future goals and his desire to pursue them, we worked to fulfill his requests and have come to a resolution that we feel is mutually beneficial to both Danny and our organization,” Sixers GM Sam Hinkie said in a statement. “We wish Danny the best in the next phase of his career.”

The Pacers traded Granger to the Sixers at the deadline, but Granger was upset upon hearing the news. The Sixers hesitated as they pondered retaining the former All-Star for a possible sign-and-trade in the summer, but they wound up acquiescing to his desires. It’s not clear how much money Granger is forfeiting from his more than $14MM salary.

The Creative Artists Agency client figures to be the prize of the buyout market, even though one GM told Sam Amico of Fox Sports Ohio that he thinks the ninth-year veteran is “done” after injuries that have plagued him the last two seasons. Chris Mannix of reiterates Stein’s report that the Spurs and Clippers are the front runners, having heard that from executives with other clubs (Twitter link).

View Comments (4)