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

Re: [PATCH v2 2/2] bash completion: Support "divergence from upstream" warnings in __git_ps1

From
SZEDER Gábor <szeder@ira.uka.de>
Date
Jun 14, 2010, 12:36 UTC
Message-ID
<20100614123633.GN4640@neumann>
In-Reply-To
<93842467ca22405712cab23a9b3920c106df0f17.1276336602.git.trast@student.ethz.ch>
Hi,
On Sat, Jun 12, 2010 at 11:59:11AM +0200, Thomas Rast wrote:
Show 15 quoted lines
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 57245a8..a6cb435 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -42,6 +42,17 @@
>  #       set GIT_PS1_SHOWUNTRACKEDFILES to a nonempty value. If there're
>  #       untracked files, then a '%' will be shown next to the branch name.
>  #
> +#       If you would like to see the difference between HEAD and its upstream,
> +#       set GIT_PS1_SHOWUPSTREAM to one of the following:
> +#           git          use @{upstream}
> +#           svn          attempt to DWIM svn upstream for normal and --stdlayout
> +#           ref <ref>    unconditionally use <ref>
> +#           eval <code>  evaluate <code> which should print the commit to use
> +#       Any other value DWIMs either svn or git, preferring svn if configured.
Something like this should go in there somewhere:
  The bash.showUpstream config variable can be used to override the 
  value of GIT_PS1_SHOWUPSTREAM on a per-repository basis.
Show 7 quoted lines
> +#
> +#       The difference will be shown as, e.g., "u+7-5" meaning that you are 7
> +#       commits ahead of and 5 commits behind the upstream.
> +#
>  # To submit patches:
>  #
>  #    *) Read Documentation/SubmittingPatches
Previous: Thomas RastNext: Thomas Rast
Message 6 of 22 in “bash completion: Support "divergence from upstream" warnings in __git_ps1”
  1. 0/2 bash completion: Support "divergence from upstream" warnings in __git_ps1Thomas Rast, Jun 12, 2010
  2. 1/2 rev-list: introduce --count optionThomas Rast, Jun 12, 2010
  3. 2/2 bash completion: Support "divergence from upstream" warnings in __git_ps1Thomas Rast, Jun 12, 2010
  4. Junio C HamanoJun 14, 2010
  5. Thomas RastJun 14, 2010
  6. SZEDER GáborJun 14, 2010
  7. vger doesn't like UTF-8 from send-emailThomas Rast, Jun 12, 2010
  8. send-email: ask about and declare 8bit mailsThomas Rast, Jun 12, 2010
  9. Junio C HamanoJun 12, 2010
  10. Thomas RastJun 13, 2010
  11. Michael WittenJun 13, 2010
  12. Erik Faye-LundJun 14, 2010
  13. bash completion: Support "divergence from upstream" messages in __git_ps1Andrew Sayers, Jun 12, 2010
  14. Thomas RastJun 14, 2010
  15. [PATCHv4] bash completion: Support "divergence from upstream" messages in __git_ps1Andrew Sayers, Jun 15, 2010
  16. Junio C HamanoJun 16, 2010
  17. Thomas RastJun 16, 2010
  18. 0/2 bash completion: Support "divergence from upstream" messages in __git_ps1Andrew Sayers, Jun 17, 2010
  19. Junio C HamanoJun 18, 2010
  20. Andrew SayersJun 18, 2010
  21. 1/2 bash completion: Support "divergence from upstream" messages in __git_ps1Andrew Sayers, Jun 17, 2010
  22. 2/2 bash-completion: Fix __git_ps1 to work with "set -u"Andrew Sayers, Jun 17, 2010

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.