On Wed, Apr 22, 2015 at 7:44 PM, Michael Haggerty wrote:
> I think what you are looking for is
>
> return any(r.match(branch) for r in branches)
Yup, thats exactly what I wanted. I'll submit an updated patch
> I was also wondering why you decided to support comma-separated lists of
> regexp
list.
I pushed this change out to our production git server (its good to be
the king.) I'll obviously update here if it does anything too
unfortunate.
On Wed, Apr 22, 2015 at 6:39 PM, Michael Haggerty wrote:
> On 04/22/2015 01:04 AM, Dave Boutcher wrote:
>> Add a branches option
Add a stdout option to the config that is equivalent to the --stdout
command line option. This allows for easier debugging for a hook
Signed-off-by: Dave Boutcher
---
git-multimail/README | 5 +
git-multimail/git_multimail.py | 10 +-
2 files changed, 14 insertions(+), 1
Add a branches option to the config. Only changes
pushed to specified branches will generate emails. Changes to tags
will continue to generate emails.
Signed-off-by: Dave Boutcher
---
git-multimail/README | 7 +++
git-multimail/git_multimail.py | 44
We have a very log list of recipients...displaying that list
on every push is annoying
Add an option to prevent printing the list of email addresses from
the hook
Signed-off-by: Dave Boutcher
---
git-multimail/README | 3 +++
git-multimail/git_multimail.py | 11 ++-
2 files
5 matches
Mail list logo