git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: should git push . from:to work?

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 2, 2007, 10:02 UTC
Message-ID
<epv25o$tpm$1@sea.gmane.org>
In-Reply-To
<20070201150545.GA30858@mellanox.co.il>
Michael S. Tsirkin wrote:
>> Quoting Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> Subject: Re: should git push . from:to work?
Show 14 quoted lines
>> On Thu, 1 Feb 2007, Michael S. Tsirkin wrote:
>> 
>> > Should I not be able to use . as a URL?
>> > git push seems to think . is a remote, not a URL:
>> 
>> You seem to be infected by the less-than-intuitive
>> "git pull ."-makes-perfect-sense camp.
> 
> Not really, I don't really care.
> 
>> Why not just do "git branch to from"?
> 
> Because I want to update am existing local branch that is different from
> what I have checked out.

But git-branch does _not_ do checkout, so you can use it to manipulate branches even if you are on different branch (even if you have different branch checked out)!

Neither git-fetch not git-push understand '.' remote; git-pull was (and is) special case to allow git-fetch+git-pull workflow.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Michael S. Tsirkin
Message 4 of 4 in “should git push . from:to work?”
  1. Michael S. TsirkinFeb 1, 2007
  2. Johannes SchindelinFeb 1, 2007
  3. Michael S. TsirkinFeb 1, 2007
  4. Jakub NarebskiFeb 2, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.