git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Ramkumar Ramachandra" <artagnon@gmail.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>,
	"Björn Gustavsson" <bgustavsson@gmail.com>,
	"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: Re: [PATCH] fetch: add new fetch.default configuration
Date: Sat, 1 Jun 2013 09:04:09 -0500	[thread overview]
Message-ID: <CAMP44s1_yQ+y5eupd3vbhDi6be+vhkj8cSw4K2kxn5wDMFQwgA@mail.gmail.com> (raw)
In-Reply-To: <1368843536-19781-1-git-send-email-felipe.contreras@gmail.com>

On Fri, May 17, 2013 at 9:18 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> When the user has an upstream branch configured to track a remote
> tracking branch:
>
>   % git checkout --set-upstream-to github/master
>
> Doing a 'git fetch' without any arguments would try to fetch 'github',
> because it's configured as current branch's remote
> (branch.<current>.remote).
>
> However, if we do something slightly different:
>
>   % git checkout --set-upstream-to master
>
> Doing a 'git fetch' without any arguments would try to fetch the remote
> '.', for the same reason.

What happened to this? Didn't you want big commit messages?

-- 
Felipe Contreras

      parent reply	other threads:[~2013-06-01 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18  2:18 [PATCH] fetch: add new fetch.default configuration Felipe Contreras
2013-05-18 18:43 ` Ramkumar Ramachandra
2013-05-18 22:20   ` Felipe Contreras
2013-05-19 11:51     ` Ramkumar Ramachandra
2013-05-19 12:15       ` Felipe Contreras
2013-05-19 12:26         ` Ramkumar Ramachandra
2013-05-19 12:37           ` Felipe Contreras
2013-05-19  2:42 ` Eric Sunshine
2013-06-01 14:04 ` Felipe Contreras [this message]

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=CAMP44s1_yQ+y5eupd3vbhDi6be+vhkj8cSw4K2kxn5wDMFQwgA@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=bgustavsson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    /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).