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

Re: [PATCH] Fix contrib/hooks/post-receive-email for new branch with no new commits

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 10, 2009, 16:30 UTC
Message-ID
<7vbptantj2.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<m3ab8uuwfg.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
> +	this_branch=$refname
> +	other_branches=$(git for-each-ref --format='%(refname)' refs/heads/ |
> +               grep -v $this_branch)
This is still not quite right.  grep -F -v "$this_branch" perhaps?
Previous: Johannes SchindelinNext: Pat Notz
Message 4 of 5 in “Fix contrib/hooks/post-receive-email for new branch with no new commits”
  1. Fix contrib/hooks/post-receive-email for new branch with no new commitsPat Notz, Feb 10, 2009
  2. Jakub NarebskiFeb 10, 2009
  3. Johannes SchindelinFeb 10, 2009
  4. Junio C HamanoFeb 10, 2009
  5. Fix contrib/hooks/post-receive-email for new duplicate branchPat Notz, Feb 10, 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.