From: Linus Torvalds <torvalds@linux-foundation.org>
To: ischis2@cox.net
Cc: Junio Hamano C <gitster@pobox.com>,
Git List Mailing <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)
Date: Thu, 22 Nov 2018 08:05:07 -0800 [thread overview]
Message-ID: <CAHk-=whO9=J-+4BuzV1WWVE1DRTceTRSeXTpXQjJtSz=NRmqrw@mail.gmail.com> (raw)
In-Reply-To: <2775489.rJSdpldxyu@thunderbird>
On Wed, Nov 21, 2018 at 6:08 PM Stephen P. Smith <ischis2@cox.net> wrote:
>
> Picking up someones stalled patch is one thing, picking up Linus' patch is in
> a different league.
No, I think it works the other way - my random patches are likely the
_least_ important ones, simply because I can carry them around in my
own tree anyway, and my workflows may be odd by most git standards.
If I'm the only user of the "human" date format, then Junio is
absolutely right to not move it to the main branch.
I have some other private patches in my tree that have been mentioned
on the list but that nobody else got excited about:
- Add 'human' date mode
- Make 'git gc --prune=now' mean 'prune after start of command'
- ls-remote: add "--diff" option to show only refs that differ
none of which are in the least important, but that I find personally useful.
Linus
next prev parent reply other threads:[~2018-11-22 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 9:00 What's cooking in git.git (Nov 2018, #06; Wed, 21) Junio C Hamano
2018-11-21 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-22 17:53 ` Jeff King
2018-11-22 18:36 ` Ævar Arnfjörð Bjarmason
2018-11-24 12:09 ` Jeff King
2018-11-25 2:02 ` Junio C Hamano
2018-11-26 18:13 ` Jeff King
2018-11-24 2:11 ` Junio C Hamano
2018-11-24 12:06 ` Jeff King
2018-11-21 20:11 ` js/vsts-ci, was " Johannes Schindelin
2018-11-21 23:54 ` Stephen P. Smith
2018-11-22 1:06 ` Junio C Hamano
2018-11-22 2:08 ` Stephen P. Smith
2018-11-22 16:05 ` Linus Torvalds [this message]
2018-11-22 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-26 21:57 ` Stefan Beller
2018-11-26 23:34 ` Junio C Hamano
2018-12-05 22:04 ` Matthew DeVore
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHk-=whO9=J-+4BuzV1WWVE1DRTceTRSeXTpXQjJtSz=NRmqrw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ischis2@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).