thanks a lot for that precisely description.
Best Regards,
Oliver
On Tue, Jun 16, 2015 at 11:23 PM, Eric Wong wrote:
> (re-adding mutt-users to Cc:, there's no Mail-Followup-To: or Reply-To:
> in the header and I'm new to this list (but not mutt) so I'll just
> follow git and linux-kernel mail
On 15/06/15, Eric Wong wrote:
> Oliver Graute wrote:
> > I would like to apply patches received from a public mailinglist to a
> > git repository. There for i'am looking for an easy to handle maintainer
> > workflow for mutt and git. How do maintainers of known open source
> > projects handle thes
(re-adding mutt-users to Cc:, there's no Mail-Followup-To: or Reply-To:
in the header and I'm new to this list (but not mutt) so I'll just
follow git and linux-kernel mailing list (LKML) conventions for now)
Oliver Graute wrote:
> On 15/06/15, Eric Wong wrote:
> > Oliver Graute wrote:
> > > I w
Oliver Graute wrote:
> Hello,
>
> I would like to apply patches received from a public mailinglist to a
> git repository. There for i'am looking for an easy to handle maintainer
> workflow for mutt and git. How do maintainers of known open source
> projects handle these workflow with incoming pa
Hello,
I would like to apply patches received from a public mailinglist to a
git repository. There for i'am looking for an easy to handle maintainer
workflow for mutt and git. How do maintainers of known open source
projects handle these workflow with incoming patches?
Best regards,
Oliver
