git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Yann Dirson <ydirson@altern.org>
Subject: Re: [PATCH] rebase: use @{upstream} if no upstream specified
Date: Tue, 8 Feb 2011 22:17:37 -0600	[thread overview]
Message-ID: <20110209041737.GD24346@elie> (raw)
In-Reply-To: <alpine.DEB.2.00.1102081959210.14152@debian>

Martin von Zweigbergk wrote:

> Maybe something like this on top? I put it in git-parse-remote.sh for
> now.

Thanks.  That sounds like a good place.

> Changes to the text compared to before:
>
>  * "remote branch" became "upstream branch", even for git pull

Sensible for pull --rebase.  I'm not so sure about plain pull --- what
if I am upstream and pulling from downstream?

>  * "You asked me to pull" became "You asked me to merge" or "You asked
>    me to rebase", even for git pull

"To pull" would be clearer if the reader is new and unfamiliar with
the details.

>  * Now printed to stderr, because I simply didn't think about it. Good
>    or bad?

If this were a new message, I'd say stderr is better.

As is, the change to stderr seems relatively harmless, though I haven't
thought about it deeply.  But a part of me likes to see functional
changes isolated in separate commits to make tracking down bugs a
little easier.

Hope that helps,
Jonathan

  reply	other threads:[~2011-02-09  4:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08  0:37 [PATCH] rebase: use @{upstream} if no upstream specified Martin von Zweigbergk
2011-02-08 17:46 ` Sverre Rabbelier
2011-02-08 18:23   ` Martin von Zweigbergk
2011-02-08 18:27     ` Sverre Rabbelier
2011-02-08 22:05     ` Jonathan Nieder
2011-02-09  0:28       ` Martin von Zweigbergk
2011-02-09  1:50         ` Martin von Zweigbergk
2011-02-09  4:17           ` Jonathan Nieder [this message]
2011-02-10  1:15             ` Martin von Zweigbergk
2011-02-10  1:54 ` Martin von Zweigbergk
2011-02-10  2:25   ` Junio C Hamano
2011-02-10  2:46     ` Martin von Zweigbergk

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=20110209041737.GD24346@elie \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.von.zweigbergk@gmail.com \
    --cc=srabbelier@gmail.com \
    --cc=ydirson@altern.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 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).