If you commit them to the github repo its obvious though that those newer
changes will get pulled in with the pull request. When making changes and
filing pull requests I would finish up lets say for example you got VST's
to work all that work i commit it to the local repo then the remote repo
then file a pull request then keep working on other things.
On Thu, May 8, 2014 at 10:36 PM, Tres Finocchiaro <
tres.finocchi...@gmail.com> wrote:
> On Thu, May 8, 2014 at 4:32 PM, Jonathan Aquilina
> <eagles051...@gmail.com>wrote:
>
>> After each set of change s create a pull request
>>
>
> Yes, and it is that mentality that I was operating from (FYI, it tosses
> those newer changes that occur after the request in without asking).
>
> -Tres
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
