On Fri, Feb 10, 2012 at 11:25, thron7 <thomas.herchenroe...@1und1.de> wrote:

>
> On 02/10/2012 12:11 PM, John Spackman wrote:
> >
> > This is the commit:
> >
> https://github.com/johnspackman/qooxdoo/commit/e9171f5f627db8fdb0c71a73722c2bc045435b5d
> >
> >
> > Also, I tried to create a new pull request for this but my commit has
> > been attached to the pull request from a few days ago – that seems a
> > little confusing as the two commits have nothing to do with each
> > other! Have I done something wrong at github or is this normal?
>
> Indeed, this commit is already affiliated with your previous pull
> request. Maybe pull requests operate on the entire repository, not just
> single commits?!
>

The intended workflow with git is to create a new branch for each new
feature you want to work on. I believe that if you issue pull requests from
different branches, they will end up as unique pull requests, whereas if
you issue pull requests from the same branch, it's seen as an enhancement
to the previous work, so is merged with the original pull request. That's
probably worth experimenting with to determine exactly what the policy is
at github.

Derrell
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to