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

Re: [PATCH v3 0/8] Introduce publish tracking branch

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 11, 2014, 18:49 UTC
Message-ID
<vpqeh13aegs.fsf@anie.imag.fr>
In-Reply-To
<1397239151-2391-1-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> * Override other configurations (such as push.default)

I think I convinced myself that this is the right way to go since my last message. After all, "push.default" is, by definition, just a default.

Show 13 quoted lines
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -764,6 +764,13 @@ branch.<name>.mergeoptions::
>  	option values containing whitespace characters are currently not
>  	supported.
>  
> +branch.<name>.push::
> +	Defines, together with branch.<name>.pushremote, the publish branch for
> +	the given branch. It tells 'git push' which branch to push to, and
> +	overrides any other configurations, such as push.default. It also tells
> +	commands such as 'git status' and 'git branch' which remote branch to
> +	use for tracking information (commits ahead and behind).
> +
Good.

I think this text should mention the @{publish} shorthand too. Stg like "This branch can be refered to as @{publish} when specifying revision (see linkgit:gitrevisions[7])."

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Felipe Contreras
Message 11 of 11 in “Introduce publish tracking branch”
  1. 0/8 Introduce publish tracking branchFelipe Contreras, Apr 11, 2014
  2. 1/8 t5516 (fetch-push): fix test restorationFelipe Contreras, Apr 11, 2014
  3. 2/8 Add concept of 'publish' branchFelipe Contreras, Apr 11, 2014
  4. Junio C HamanoApr 11, 2014
  5. 3/8 branch: add --set-publish-to optionFelipe Contreras, Apr 11, 2014
  6. 4/8 push: add --set-publish optionFelipe Contreras, Apr 11, 2014
  7. 5/8 branch: display publish branchFelipe Contreras, Apr 11, 2014
  8. 6/8 sha1_name: cleanup interpret_branch_name()Felipe Contreras, Apr 11, 2014
  9. 7/8 sha1_name: simplify track findingFelipe Contreras, Apr 11, 2014
  10. 8/8 sha1_name: add support for @{publish} marksFelipe Contreras, Apr 11, 2014
  11. Matthieu MoyApr 11, 2014

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.