Re: [LMMS-devel] Git/Pull Requests Question

[Lukas W.]

Hi,

The recommended way with git is to have a separate branch for each issue
(e.g. "master-new_awesome_plugin", "master-iss235"). You'll then have to
submit a pull request for each branch.

- Lukas


2014-05-08 21:53 GMT+02:00 Tres Finocchiaro <tres.finocchi...@gmail.com>:

> Question,
>
> As I'm making changes to my branch they all seem to land into my last pull
> request.  Is this normal?
>
> I'd much rather have one pull requests for each chunk of changes.
>
> What am I missing?
>
> https://github.com/LMMS/lmms/pull/694
>
> I had to go back and fix the pull request description to match that of the
> changes.  I don't like this behavior.
>
> -Tres
> - tres.finocchi...@gmail.com
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; 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
>
>

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; 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