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: Wed, 16 Mar 2016 15:51:09 -0700 [thread overview]
Message-ID: <xmqqlh5i2g0y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqy49i2hhe.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 16 Mar 2016 15:19:41 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> The list is my personal collection of "leftover" things, i.e. topics
> that were raised on the list, perhaps already discussed or perhaps
> nobody thought them interesting, that I found when re-reading the
> past list traffic that did not reach a useful conclusion to result
> in a patch (or resolution, a shared understanding, that it is not a
> good idea). Getting added to the list should not be a goal.
>
> Your message is perhaps the least effective way to add an item to
> the list. It hasn't been discussed here, nobody seems to have felt
> it is a good idea, and I didn't think it is particularly interesting
> myself (at least not yet).
Having said that, I could use help in maintaining the collection.
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.
* Adding new entry after scanning past list traffic and finding a
still unresolved topic that "died down" is relatively easy.
* Removing existing entries because the topic was revived on the
list and completed is _hard_, as that is merely an administrative
overhead to me.
Moving it to a public wiki would lose the first point, which is a
benefit.
Merely making it public does not guarantee that the third point
(i.e. clean-up) would happen more easily unless we have volunteers.
It is likely that the "leftover bits" list would go stale just like
other people's wikis or bug trackers.
On the other hand, if we do have volunteers who are scanning for
"stale" items in the "leftover bits" list to tell me "that item was
done with commit c0ffee1eaf" and that would help me quite a bit
without being it a public wiki/bug tracker.
next prev parent reply other threads:[~2016-03-16 22:51 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 [this message]
2016-03-16 23:18 ` Stefan Beller
2016-03-17 7:31 ` Junio C Hamano
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=xmqqlh5i2g0y.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