threads / discuss / 17129

git-patches list?

Subject: git-patches list?

## tl;dr

7 messages between Jan 12, 2009 and Jan 19, 2009.

replies: 6people: 5as markdown or json

Junio C Hamano· Jan 12, 2009, 23:54 UTC · re: Akira Kitada · lore

Re: git-patches list?

Akira Kitada <akitada@gmail.com> writes:
> Can I propose having another mailing list for posting patches to avoid
> daily mail flood to this list?
>
> Yes, I can filter out the emails but still...

This list has always been the only place where git development happens. It would make the development very awkward to set up another list only for patches, forbid patches to be sent to anywhere but that new list, but still discuss the patches on this list.

It does not make much sense to me.

Consider what you would do when you see a problem somebody is having on this list, and wanted to respond with a quick "this may fix it" patch? Should you be sending that to the patches list, and sending a separate message to this list saying that you have a potential fix in mind you would want to discuss here, but the patches list rule mandated that you had to send the patch to the other list, asking people who are reading this list to look at the other list as well?

And no, having a separate "user list" won't solve the above problem either and that is not what I am suggesting.

Not that I am seeing any problem right now; I am saying that the split list as you suggest _will_ create problems.

Andreas Ericsson· Jan 13, 2009, 08:26 UTC · re: Junio C Hamano · lore

Re: git-patches list?

Junio C Hamano wrote:
Show 14 quoted lines
> Akira Kitada <akitada@gmail.com> writes:
> 
>> Can I propose having another mailing list for posting patches to avoid
>> daily mail flood to this list?
>>
>> Yes, I can filter out the emails but still...
> 
> This list has always been the only place where git development happens.
> It would make the development very awkward to set up another list only for
> patches, forbid patches to be sent to anywhere but that new list, but
> still discuss the patches on this list.
> 
> It does not make much sense to me.
> 
I agree.

If any new list is to be introduced, it would only make sense to make it a read-only "what's new" list, for the various people that want to know what might break/be fixed in new versions but really don't care about the discussion that lead to that decision.

Is that what you were after, Akira?
-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Johannes Schindelin· Jan 13, 2009, 11:02 UTC · re: Andreas Ericsson · lore

Re: git-patches list?

Hi,
On Tue, 13 Jan 2009, Andreas Ericsson wrote:
Show 22 quoted lines
> Junio C Hamano wrote:
> > Akira Kitada <akitada@gmail.com> writes:
> > 
> > > Can I propose having another mailing list for posting patches to avoid
> > > daily mail flood to this list?
> > >
> > > Yes, I can filter out the emails but still...
> > 
> > This list has always been the only place where git development happens.
> > It would make the development very awkward to set up another list only for
> > patches, forbid patches to be sent to anywhere but that new list, but
> > still discuss the patches on this list.
> > 
> > It does not make much sense to me.
> > 
> 
> I agree.
> 
> If any new list is to be introduced, it would only make sense to make it
> a read-only "what's new" list, for the various people that want to know
> what might break/be fixed in new versions but really don't care about the
> discussion that lead to that decision.
If that's what you want, I suggest having a look at 
	http://gitrss.q42.co.uk/
I am sure that Julian can be convinced to filter "[PATCH", too.

Ciao, Dscho

Akira Kitada· Jan 13, 2009, 15:55 UTC · re: Junio C Hamano · lore

Re: git-patches list?

This list seems to be used as a bug tracker, discussing git development, user questions, announcement etc. I thought this is so unusual list that something should be wrong here, but it turned out that it looks working right in mysteryous way. I take that back now. Hmm, interesting...

Thanks,
On Tue, Jan 13, 2009 at 8:54 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 28 quoted lines
> Akira Kitada <akitada@gmail.com> writes:
>
>> Can I propose having another mailing list for posting patches to avoid
>> daily mail flood to this list?
>>
>> Yes, I can filter out the emails but still...
>
> This list has always been the only place where git development happens.
> It would make the development very awkward to set up another list only for
> patches, forbid patches to be sent to anywhere but that new list, but
> still discuss the patches on this list.
>
> It does not make much sense to me.
>
> Consider what you would do when you see a problem somebody is having on
> this list, and wanted to respond with a quick "this may fix it" patch?
> Should you be sending that to the patches list, and sending a separate
> message to this list saying that you have a potential fix in mind you
> would want to discuss here, but the patches list rule mandated that you
> had to send the patch to the other list, asking people who are reading
> this list to look at the other list as well?
>
> And no, having a separate "user list" won't solve the above problem either
> and that is not what I am suggesting.
>
> Not that I am seeing any problem right now; I am saying that the split
> list as you suggest _will_ create problems.
>
Felipe Contreras· Jan 14, 2009, 08:44 UTC · re: Akira Kitada · lore

Re: git-patches list?

On Tue, Jan 13, 2009 at 5:55 PM, Akira Kitada <akitada@gmail.com> wrote:
Show 6 quoted lines
> This list seems to be used as a bug tracker, discussing git development,
> user questions, announcement etc.
> I thought this is so unusual list that something should be wrong here,
> but it turned out that it looks working right in mysteryous way.
> I take that back now.
> Hmm, interesting...
Yes, it's definitely not the norm on other projects, but perhaps it should be.

That's how the linux kernel mailing list works. There are other mailing lists for the different sub-systems, but there's no separation between bugs, discussion and patches, which makes sense, because quite often bugs and patches trigger discussions, and bug discussions trigger patches.

Following this approach perhaps it would make sense to create a separate mailing list for jgit and similar stuff.

-- 
Felipe Contreras

← back to recent threads