From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: An idea for the "Leftover Bits": rebase -x to imply -i
Date: Thu, 17 Mar 2016 00:31:34 -0700 [thread overview]
Message-ID: <xmqqbn6d36i1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZC0AAz=cm59ys1L_Axj1_HLvcTqrMrfNrOHoA3Ef7a5A@mail.gmail.com> (Stefan Beller's message of "Wed, 16 Mar 2016 16:18:10 -0700")
Stefan Beller <sbeller@google.com> writes:
> On Wed, Mar 16, 2016 at 3:51 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> A few "characteristics" of that list, that cannot be updated by
>> anybody but me (because it is just my personal collection after all)
>> are:
>>
>> * I do not have to worry about useless new entries that do not
>> align the overall system design getting added by clueless people.
>
> As it is your personall collection and you're the maintainer, I thought
> of this as a collection with maintainers blessing, i.e. if the code&tests
> are not too shoddy a patch will get accepted (read as: On that list there
> are no bullet points with fundamental design issues). Why would you
> add things to that list if you'd not agree with them?
If it was not clear, I didn't mean these three are all bad things.
In fact, this first of the three "characteristics" is a good thing.
Random people are not allowed to throw random things into it.
>> * Adding new entry after scanning past list traffic and finding a
>> still unresolved topic that "died down" is relatively easy.
>
> As the notes in Documentation/howto/maintain-git.txt indicate, you're
> scanning the list anyway, so offering help in this point may be moot.
The scanning of the list for new topics (to further discuss and pick
patches to queue) and the scanning of the list for "died down"
threads are two completely separate activities. If somebody with
good taste can do the latter when I am too busy elsewhere by
pointing out "what happened to this thread? It seems that nobody is
interested enough to pursue it right now, so perhaps it is a good
time to add it to 'leftover bits' list?", that would be helpful.
And as you agreed, pointing out "done" items to remove would also be
helpful.
Thanks.
next prev parent reply other threads:[~2016-03-17 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 21:12 An idea for the "Leftover Bits": rebase -x to imply -i Stefan Beller
2016-03-16 22:19 ` Junio C Hamano
2016-03-16 22:51 ` Junio C Hamano
2016-03-16 23:18 ` Stefan Beller
2016-03-17 7:31 ` Junio C Hamano [this message]
2016-03-16 22:33 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbn6d36i1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox