From: Thomas Rast <trast@student.ethz.ch>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Sean Estabrooks <seanlkml@sympatico.ca>, <git@vger.kernel.org>
Subject: Re: [PATCH] pull: refuse complete src:dst fetchspec arguments
Date: Wed, 21 Oct 2009 10:05:27 +0200 [thread overview]
Message-ID: <200910211005.29053.trast@student.ethz.ch> (raw)
In-Reply-To: <20091021031528.GB18997@atjola.homenet>
Björn Steinbrink wrote:
> One (maybe important) difference there is that the "pull" gets you:
>
> Merge branch 'pu' of git://git.kernel.org/pub/scm/git/git
>
> Even with "master:tmp". But with fetch+merge (storing in refs/remotes):
>
> Merge remote branch 'tmp'
What if any combination of fetch and merge always gave you the long
form? After all, even if you do have a tracking branch for whatever
you are merging, that information is probably useless and it would be
nicer if all of the following resulted in the long form:
* git fetch git://git.kernel.org/pub/scm/git/git pu
git merge FETCH_HEAD
* git remote add origin git://git.kernel.org/pub/scm/git/git
git fetch origin
git merge origin/pu
* git fetch git://git.kernel.org/pub/scm/git/git pu:tmp
git merge tmp
and so on.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-10-21 8:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:23 [PATCH] pull: refuse complete src:dst fetchspec arguments Thomas Rast
2009-10-20 18:37 ` [RFC! PATCH] " Thomas Rast
2009-10-20 19:29 ` [PATCH] " Wesley J. Landaker
2009-10-20 20:30 ` Sean Estabrooks
2009-10-20 21:11 ` Junio C Hamano
2009-10-21 0:15 ` Daniel Barkalow
2009-10-21 0:29 ` Sean Estabrooks
2009-10-21 0:55 ` Daniel Barkalow
2009-10-21 1:35 ` Sean Estabrooks
2009-10-21 3:15 ` Björn Steinbrink
2009-10-21 4:32 ` Daniel Barkalow
2009-10-21 8:05 ` Thomas Rast [this message]
2009-10-23 2:54 ` Jeff King
2009-10-23 3:43 ` Daniel Barkalow
2009-10-24 0:49 ` Jeff King
2009-10-24 1:22 ` Junio C Hamano
2009-10-21 8:06 ` Thomas Rast
2009-11-15 12:24 ` Thomas Rast
2009-11-15 20:22 ` Junio C Hamano
2009-12-29 11:05 ` Nanako Shiraishi
2009-12-29 16:58 ` Junio C Hamano
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=200910211005.29053.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=B.Steinbrink@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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.