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

Re: [PATCH 1/3] git-multimail: Add an option to filter on branches

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Apr 22, 2015, 10:39 UTC
Message-ID
<55377A60.707@alum.mit.edu>
In-Reply-To
<1429657487-10809-1-git-send-email-daveboutcher@gmail.com>
On 04/22/2015 01:04 AM, Dave Boutcher wrote:
> Add a branches option to the config.  Only changes
> pushed to specified branches will generate emails. Changes to tags
> will continue to generate emails.

Thanks for the patches. Patches 2 and 3 seem uncontroversial, so I already merged them. Patch 1 is more interesting, and there have been other proposals for similar features, so I created a pull request for it:

    https://github.com/git-multimail/git-multimail/pull/75

(Note the new URL--I just created a GitHub "organization" for git-multimail to make it easier for other people to get involved. More info soon...)

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
Previous: Dave BoutcherNext: Dave Boutcher
Message 4 of 7 in “git-multimail: Add an option to filter on branches”
  1. 1/3 git-multimail: Add an option to filter on branchesDave Boutcher, Apr 21, 2015
  2. 2/3 git-multimail: Add a quiet option to prevent outputting email addresses from hookDave Boutcher, Apr 21, 2015
  3. 3/3 git-multimail: Add stdout option to configDave Boutcher, Apr 21, 2015
  4. Michael HaggertyApr 22, 2015
  5. Dave BoutcherApr 22, 2015
  6. Michael HaggertyApr 22, 2015
  7. Dave BoutcherApr 23, 2015

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.