From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git log: add '--merges' flag to match '--no-merges'
Date: Mon, 29 Jun 2009 11:15:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906291112520.3605@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.01.0906291015210.3605@localhost.localdomain>
On Mon, 29 Jun 2009, Linus Torvalds wrote:
>
> So this just adds a '--merges' flag that _only_ shows merges.
Side note: if somebody wants to make this flag be called "--merges-only",
and then adds a "--merges" flag that clears both the no_merges and
merges_only flag, I wouldn't complain. That _might_ be useful to override
default behaviour (say, if some alias/command were to default to not
showing merges, then adding "--merges" would make it show all commits).
Dunno. I don't personally much care, but I thought I'd mention it as an
alternative approach to this issue.
Linus
prev parent reply other threads:[~2009-06-29 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 17:28 git log: add '--merges' flag to match '--no-merges' Linus Torvalds
2009-06-29 18:15 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0906291112520.3605@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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