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:19:41 -0700 [thread overview]
Message-ID: <xmqqy49i2hhe.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZg3QkfjB1hwZKRS9Hqg-1H=kQwuwByX_rAMzveXtnp7Q@mail.gmail.com> (Stefan Beller's message of "Wed, 16 Mar 2016 14:12:39 -0700")
Stefan Beller <sbeller@google.com> writes:
> here is an additional ideas for the "Leftover Bits" on git-blame.blogspot.com
> (Is there another way of contributing these, such as sending a patch
> against some
> repository? Or any other way which may bother you less?)
A message "Subject: [RFC] ..." that asks "Wouldn't it be wonderful
if command X is extended to work like this way?", without even
mentioning "leftover bits", would be far more useful. Instead of
going nowhere waiting for the next round of "leftover sweep" picks
it up to add it to my "leftover bits" list, it may even find a
traction here ;-).
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).
next prev parent reply other threads:[~2016-03-16 22:26 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 [this message]
2016-03-16 22:51 ` Junio C Hamano
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=xmqqy49i2hhe.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