All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: tools@linux.kernel.org
Subject: b4 doesn't allow remote tracking branches
Date: Sun, 12 Feb 2023 20:26:57 -0700	[thread overview]
Message-ID: <87k00mdz3y.fsf@tromey.com> (raw)

I tried to do:

    b4 prep -e origin/master

... but it gave me some error.
Instead I had to do 'b4 prep -e master'.

Then, today, I forgot to checkout master + rebase before doing a 'b4
send', so it sent some random patches from origin/master as part of my
series.

I think it would be nice if b4 let me use a remote branch as the base
for my branch.  'git rebase' has no issue with this.

thanks,
Tom

             reply	other threads:[~2023-02-13  3:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  3:26 Tom Tromey [this message]
2023-02-22  2:12 ` b4 doesn't allow remote tracking branches Philippe Blain

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=87k00mdz3y.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=tools@linux.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.