On Jul 10, 2015 12:11 PM, "Ian Jackson"
wrote:
>
> Dimitri John Ledkov writes ("Re: GitHub “pull request” is proprietary,
incomp atible with Git ‘request-pull ’"):
> > What you have described here is github pull requests =) they use
> > refs/pull/# namespace though, so one needs to tweak fetch con
Dimitri John Ledkov writes ("Re: GitHub “pull request” is proprietary, incomp
atible with Git ‘request-pull ’"):
> What you have described here is github pull requests =) they use
> refs/pull/# namespace though, so one needs to tweak fetch config to
> get them all.
Except that (a) we don't have a
On Tue, 2015-04-21 at 13:45 +0100, Ian Jackson wrote:
> Well, the git-send-email patchbomb workflow is pretty ugly too in many
> respects. I can see why some people don't much like it. [1]
I began with git send-email, but the email client of the person in
question did not allow getting emails ou
Paul Wise writes ("Re: GitHub “pull request” is proprietary, incomp atible with
Git ‘request-pull’"):
> Just an FYI, there are Debian folks who reject patches to Debian
> services that are sent via git send-email rather than github pull
> requests. Personally I am disappointed by this.
Well, the
4 matches
Mail list logo