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

Re: git push should automatically push to remote tracking branch

From
Tomas Carnecky <tom@dbservice.com>
Date
Oct 18, 2009, 23:11 UTC
Message-ID
<1B59440B-5929-4AB9-82C7-05188DC4F959@dbservice.com>
In-Reply-To
<ee22b09e0910181320j15a273e8vc510801c890b93a9@mail.gmail.com>
On Oct 18, 2009, at 10:20 PM, Mohit Aron wrote:
Show 27 quoted lines
> Hello,
>
> I've been using git for around a year now and I'm continuing to find
> the 'git push' API rather cumbersome. My workflow is as follows. I
> typically have a local branch track a remote branch and want to pull
> and push changes back and forth. The names of the local and remote
> branches are different. Even so, while 'git pull' is enough to pull
> changes, 'git push' is not. Instead, the pull requires a full refspec
> to be specified which gets real cumbersome and error prone.
>
> Say my local branch name is foo and it is tracking a remote release
> branch of a product. Say the remote's name is origin and corresponding
> branch there is 6.1. 'git pull' nicely fetches and merges changes
> submitted by others in the remote branch to my branch foo. However, to
> do a push, I need to call:
>
>       git push origin HEAD:6.1
>
> Since my local branch has been setup to track the remote branch, I
> shouldn't have to specify all this in the 'git push' command. It'll be
> great if 'git push' were to support a variant that automatically
> allows pushing to the remotely tracked branch. This is the typical
> workflow with other version control systems too.
>
> If anyone knows a simpler alternative I can use in Git, please let me
> know. Otherwise, it'll be great if such a feature could be added to
> Git in the future.
$ git config push.default tracking
tom
Previous: Mohit AronNext: Mohit Aron
Message 2 of 4 in “git push should automatically push to remote tracking branch”
  1. Mohit AronOct 18, 2009
  2. Tomas CarneckyOct 18, 2009
  3. Mohit AronOct 19, 2009
  4. Jeff KingOct 19, 2009

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.