From: Junio C Hamano <gitster@pobox.com>
To: "Marcel Svitalský" <marcel.svitalsky@gmail.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org
Subject: Re: Bugreport
Date: Wed, 12 Aug 2026 10:04:24 -0700 [thread overview]
Message-ID: <xmqqik5fxobr.fsf@gitster.g> (raw)
In-Reply-To: <f4e39b04-b6dd-4b83-9103-8a1c98019dce@gmail.com> ("Marcel Svitalský"'s message of "Wed, 12 Aug 2026 14:59:52 +0200")
Marcel Svitalský <marcel.svitalsky@gmail.com> writes:
> I see, thank you. Is this a new feature? I've been using this command
> for years
> and today is the first time I am seeing this. Also, is there another
> flag instead of
> `--all` that would just include the actual commits only?
--branches
--tags
--remotes
next prev parent reply other threads:[~2026-08-12 17:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 12:31 Bugreport Marcel Svitalský
2026-08-12 12:54 ` Bugreport Kristoffer Haugsbakk
2026-08-12 12:59 ` Bugreport Marcel Svitalský
2026-08-12 13:14 ` Bugreport D. Ben Knoble
2026-08-12 13:36 ` Bugreport Marcel Svitalský
2026-08-12 17:04 ` Junio C Hamano [this message]
2026-08-12 17:26 ` Bugreport Marcel Svitalský
2026-08-12 17:03 ` Bugreport Junio C Hamano
[not found] <AMDPR08MB11409C5DC2EA9B3D8C71FC12BED82A@AMDPR08MB11409.eurprd08.prod.outlook.com>
2026-01-11 17:05 ` Bugreport do Carmo Lucas, Dr. Amilcar (T-PSC)
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 13:25 Bugreport Frank Schwidom
2024-01-19 23:14 ` Bugreport brian m. carlson
2023-10-24 20:40 bugreport galo joel
2023-11-20 8:36 ` bugreport Thomas Guyot
2020-12-02 10:08 bugreport Ole M
2020-12-02 16:25 ` bugreport Stefan Haller
2012-09-18 13:13 bugreport Dmitriy Bukach
2005-04-12 18:11 Bugreport Amelia Nilsson
2005-04-12 22:21 ` Bugreport Chris Wright
2004-07-27 13:08 bugreport Artem B. Bityuckiy
2004-07-27 13:22 ` bugreport Thomas Gleixner
2004-07-27 14:40 ` bugreport Artem B. Bityuckiy
2004-07-27 17:31 ` bugreport Thomas Gleixner
2004-07-28 6:41 ` bugreport Artem B. Bityuckiy
2004-07-29 19:56 ` bugreport David Woodhouse
2004-07-26 11:16 bugreport Artem Bityuckiy
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=xmqqik5fxobr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=marcel.svitalsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.