From: Cary Coutant <ccoutant@google.com>
To: Richard Henderson <rth@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Joel Brobecker <brobecker@adacore.com>,
Binutils <binutils@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Experimental branches
Date: Fri, 16 Jan 2015 19:07:00 -0000 [thread overview]
Message-ID: <CAHACq4r8Wk8cmtnU=LQUWOW159w6e92N=BWxrbc8d2KGH8eCYw@mail.gmail.com> (raw)
In-Reply-To: <54B95B3B.6010901@redhat.com>
>> 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.
-cary
next prev parent reply other threads:[~2015-01-16 19:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHACq4rzgyE-2cM=UV30-1MWKHsWqwF1QdtuAujgYzFJ=8Y08A@mail.gmail.com>
2014-12-23 13:27 ` Joel Brobecker
2014-12-23 17:38 ` Cary Coutant
2014-12-23 17:42 ` H.J. Lu
2014-12-23 18:08 ` Joel Brobecker
2014-12-23 18:21 ` Cary Coutant
2014-12-23 18:26 ` H.J. Lu
2014-12-24 0:20 ` Joel Brobecker
2015-01-15 21:56 ` Cary Coutant
2015-01-15 22:48 ` H.J. Lu
2015-01-15 23:04 ` Cary Coutant
2015-01-15 23:20 ` H.J. Lu
2015-01-16 18:41 ` Richard Henderson
2015-01-16 19:07 ` Cary Coutant [this message]
2015-01-16 19:26 ` Doug Evans
2015-01-16 3:14 ` Joel Brobecker
2015-01-15 23:57 ` Alan Modra
2015-01-16 3:19 ` Joel Brobecker
2015-01-16 18:42 ` Richard Henderson
2015-01-17 4:17 ` Joel Brobecker
2015-01-17 3:24 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHACq4r8Wk8cmtnU=LQUWOW159w6e92N=BWxrbc8d2KGH8eCYw@mail.gmail.com' \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).