This is the mail archive of the
mailing list for the binutils project.
Re: Experimental branches
- From: Doug Evans <xdje42 at gmail dot com>
- To: Cary Coutant <ccoutant at google dot com>
- Cc: Richard Henderson <rth at redhat dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, Joel Brobecker <brobecker at adacore dot com>, Binutils <binutils at sourceware dot org>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Fri, 16 Jan 2015 11:26:17 -0800
- Subject: Re: Experimental branches
- Authentication-results: sourceware.org; auth=none
- References: <CAHACq4rzgyE-2cM=UV30-1MWKHsWqwF1QdtuAujgYzFJ=8Y08A at mail dot gmail dot com> <20141223132714 dot GA11973 at adacore dot com> <CAHACq4qPSC6YX_uAcT0n35QD61LxATcKhjG0BXQ-qRhQ+GU63A at mail dot gmail dot com> <CAMe9rOqGKgd2gF6FLEAO4JQuDzyQJ8DXw94eE3ckO=ZiEep+SA at mail dot gmail dot com> <20141223180802 dot GP12884 at adacore dot com> <CAHACq4ovTQCoTpXnnU1_Rpo7cR5gDwpYZkd17zfm2dwpWJNorA at mail dot gmail dot com> <CAMe9rOprFe_cqVPoz6Bd1Fh3GaBYkHyem+upZQFe=FRrQW3tfg at mail dot gmail dot com> <20141224002022 dot GQ12884 at adacore dot com> <CAHACq4pOQzXqhePkuvm_-b0dtHiwBCre2V_d3JbtotaPooN0zA at mail dot gmail dot com> <CAMe9rOofS9d8gUxa9gc07a7M=XvLF-Ps8+8o8g2O6mpPkLXJzg at mail dot gmail dot com> <CAHACq4rwn5Qxxoc2Bp-H+tSST=bMFZmt8Z-yhGiw9+DqYxdFOA at mail dot gmail dot com> <54B95B3B dot 6010901 at redhat dot com> <CAHACq4r8Wk8cmtnU=LQUWOW159w6e92N=BWxrbc8d2KGH8eCYw at mail dot gmail dot com>
On Fri, Jan 16, 2015 at 11:07 AM, Cary Coutant <firstname.lastname@example.org> wrote:
>>> But I've already pushed several commits onto the upstream branch.
>>> Everything I've read about git says don't rebase if you've already
>>> pushed your branch upstream.
>> That's if you've actually got multiple developers coordinating.
>> For solo development on branches, rebasing minimizes the state
>> difference between trunk and the branch, and so is quite handy
>> (essential?) for preparing to submit a patch set for review.
> Yes. I already had a collaborator pull from my branch, and I didn't
> want to disrupt him.
Don't worry about me! :-)
I know git well enough now to cope.
[Which isn't to dismiss your point, which is valid,
but if it's just me ...]