[gpodder] Re: gPodder 3.3.0 "Intermission" released
- From: Joseph Wickremasinghe <jnwickremasinghe@xxxxxxxxx>
- To: gpodder@xxxxxxxxxxxxx
- Date: Sun, 30 Sep 2012 10:36:44 -0700 (PDT)
Thomas,
Thanks very much. I'll make sure to do that for next time. I wanted to throw
something up on github as a work-in-progress since I'd hadn't given you an
update for a while.
I have the one-playlist-per-podcast feature working in an alpha state at the
moment, and I love it. :) I'll get it tidied up and add in the two-way sync,
then give you a single squashed commit to review.
J.
--- On Thu, 9/27/12, Thomas Perl <th.perl@xxxxxxxxx> wrote:
> From: Thomas Perl <th.perl@xxxxxxxxx>
> Subject: [gpodder] Re: gPodder 3.3.0 "Intermission" released
> To: gpodder@xxxxxxxxxxxxx
> Date: Thursday, September 27, 2012, 5:14 AM
> Hi Joseph,
>
> 2012/9/25 Joseph Wickremasinghe <jnwickremasinghe@xxxxxxxxx>:
> > I merged your 3.30 master branch into my forked repo
> since I wanted to be able to include Rafi's sort_date fix,
> but I don't know if that makes reviewing my changes more
> difficult.
>
> You can always use "git rebase" (or even "git pull
> --rebase") to
> rebase your changes on top of the current master branch,
> this makes
> the history more clear and usually also makes fixing your
> own
> changeset easier.
>
> > Let me know your thoughts, and let me know how best to
> present this in future. I'll continue working on this, and
> add in the two-way sync.
>
> The best way for me would be if you could submit these
> changes as a
> pull request against the master branch, ideally as a single
> squashed
> commit (for small changes) or as a bunch of topic patches
> against the
> master branch (again, if possible avoid merges of the master
> branch
> and rebase instead).
>
> Thanks :)
> Thomas
>
>
Other related posts:
