From: Junio C Hamano <gitster@pobox.com>
To: Issac Trotts <issac.trotts@gmail.com>
Cc: git@vger.kernel.org, Noemi Mercado <noemi@sourcegraph.com>,
Issac Trotts <issactrotts@google.com>
Subject: Re: [PATCH] log: add %S option (like --source) to log --format
Date: Fri, 11 Jan 2019 09:47:28 -0800 [thread overview]
Message-ID: <xmqqd0p3ytlb.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CANdyxMzDevigyMTCixjV7bfa-UZ1vknwxt0X=RGc6LZz7F4UXQ@mail.gmail.com> (Issac Trotts's message of "Thu, 10 Jan 2019 22:28:41 -0800")
Issac Trotts <issac.trotts@gmail.com> writes:
> Sounds good. Btw, did you queue it yet? I didn't see it at the mirror:
> https://github.com/git/git/commits/master.
No patch goes to 'master' directly.
Once we see that a patch is in reviewable shape during the mailing
list discussion, we wait for a few more days and unless there are
more issues to be addressed discovered during that period, it hits
the 'next' branch, and spends a week or so before graduating.
Before all of that happens, i.e. when a patch has not proven itself
'next'-worthy, I may pick it up to make trial merges in order to see
how it interacts with other proposed updates, which happens in the
'pu' (proposed updates) branch. As there is only limited amount of
time in a day, this obviously cannot happen to all patches sent to
the list, but I try to cover as much as possible.
You'd find it as 5ca3af27 ("log: add %S option (like --source) to
log --format", 2019-01-09) on 'pu'.
next prev parent reply other threads:[~2019-01-11 17:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 13:20 [PATCH] log: add %S option (like --source) to log --format issac.trotts
2019-01-08 22:21 ` Junio C Hamano
2019-01-11 6:28 ` Issac Trotts
2019-01-11 17:37 ` Junio C Hamano
2019-01-11 17:47 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 6:30 issac.trotts
2018-12-31 21:48 issac.trotts
2018-12-31 4:53 issac.trotts
2019-01-02 19:33 ` Junio C Hamano
2019-01-08 13:14 ` Issac Trotts
2018-12-19 8:33 issac.trotts
2018-12-21 5:24 ` Issac Trotts
2018-12-22 22:22 ` Jeff King
2018-12-25 2:12 ` Issac Trotts
2018-12-27 13:20 ` Derrick Stolee
2018-12-28 18:14 ` Junio C Hamano
2018-12-31 4:35 ` Issac Trotts
2018-12-17 6:25 Issac Trotts
2018-12-17 9:31 ` Junio C Hamano
2018-12-18 3:35 ` Issac Trotts
2018-12-17 15:59 ` Jeff King
2018-12-18 17:14 ` Issac Trotts
2018-12-19 3:47 ` Issac Trotts
2018-12-19 8:07 ` Issac Trotts
2018-12-19 17:09 ` Issac Trotts
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=xmqqd0p3ytlb.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=issac.trotts@gmail.com \
--cc=issactrotts@google.com \
--cc=noemi@sourcegraph.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.
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).