From: Jay Soffian <jaysoffian@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Kevin Ballard <kevin@sb.org>, git@vger.kernel.org
Subject: Re: [RFC] rebase: use @{upstream} if no upstream specified
Date: Mon, 15 Nov 2010 15:12:17 -0800 [thread overview]
Message-ID: <AANLkTikewL5PcUDrmOx9EXRftz4xr4ROjPLxvW7oUJi7@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=sEVHTqWqcdztcEv6kTZgscVYZWr-N0SBMRwvc@mail.gmail.com>
On Mon, Nov 15, 2010 at 3:06 PM, Martin von Zweigbergk
<martin.von.zweigbergk@gmail.com> wrote:
> do you think it is sensible to default to '@{upstream}'?
I certainly do.
j.
next prev parent reply other threads:[~2010-11-15 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 20:55 [RFC] rebase: use @{upstream} if no upstream specified Martin von Zweigbergk
2010-11-13 9:51 ` Yann Dirson
2010-11-17 2:29 ` Martin von Zweigbergk
2010-11-19 21:15 ` Jeff King
2010-11-20 0:26 ` Martin von Zweigbergk
2010-11-20 4:10 ` Jeff King
2010-11-20 13:14 ` Martin von Zweigbergk
2010-11-15 22:48 ` Kevin Ballard
2010-11-15 23:06 ` Martin von Zweigbergk
2010-11-15 23:12 ` Jay Soffian [this message]
2010-11-15 23:16 ` Kevin Ballard
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=AANLkTikewL5PcUDrmOx9EXRftz4xr4ROjPLxvW7oUJi7@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevin@sb.org \
--cc=martin.von.zweigbergk@gmail.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 NNTP newsgroup(s).