From: Leo <sdl.web@gmail.com>
To: ding@gnus.org
Subject: Is this a threading bug?
Date: Sat, 21 May 2011 15:13:08 +0800 [thread overview]
Message-ID: <m18vu0y1a3.fsf@th041140.ip.tsinghua.edu.cn> (raw)
I am running Gnus (emacs-trunk).
Viewing the thread started at Message-ID:
<1305960995-25738-1-git-send-email-gitster@pobox.com> on gmane.comp.version-control.git
Before:
R. │21-May│ Junio C Hamano │4.5k│ │┌ [PATCH v3 00/12] writing out a huge blob to working tree
. │21-May│ Junio C Hamano │5.7k│ │├─► [PATCH v3 01/12] packed_object_info_detail(): do not return a string
. │21-May│ Junio C Hamano │8.6k│ │├─► [PATCH v3 02/12] sha1_object_info_extended(): expose a bit more info
. │21-May│ Junio C Hamano │4.8k│ │├─► [PATCH v3 03/12] sha1_object_info_extended(): hint about objects in delta-base cache
. │21-May│ Junio C Hamano │4.6k│ │├─► [PATCH v3 04/12] unpack_object_header(): make it public
. │21-May│ Junio C Hamano │5.7k│ │├─► [PATCH v3 05/12] write_entry(): separate two helper functions out
. │21-May│ Junio C Hamano │9.4k│ │├─► [PATCH v3 06/12] streaming: a new API to read from the object store
. │21-May│ Junio C Hamano │8.0k│ │├─► [PATCH v3 07/12] streaming_write_entry(): use streaming API in write_entry()
. │21-May│ Junio C Hamano │4.7k│ │├─► [PATCH v3 09/12] streaming_write_entry(): support files with holes
. │21-May│ Junio C Hamano │3.7k│ │├─► [PATCH v3 08/12] convert: CRLF_INPUT is a no-op in the output codepath
. │21-May│ Junio C Hamano │6.5k│ │├─► [PATCH v3 10/12] streaming: read non-delta incrementally from a pack
. │21-May│ Junio C Hamano │5.5k│ │├─► [PATCH v3 11/12] sha1_file.c: expose helpers to read loose objects
. │21-May│ Junio C Hamano │5.8k│ │└─► [PATCH v3 12/12] streaming: read loose objects incrementally
After removing the read article "[PATCH v3 00/12] writing out a huge
blob to working tree" the thread looks like:
. │21-May│ Junio C Hamano │5.7k│ │◯ [PATCH v3 01/12] packed_object_info_detail(): do not return a string
. │21-May│ Junio C Hamano │8.6k│ │ └─► [PATCH v3 02/12] sha1_object_info_extended(): expose a bit more info
. │21-May│ Junio C Hamano │4.8k│ │ └─► [PATCH v3 03/12] sha1_object_info_extended(): hint about objects in delta-base cache
. │21-May│ Junio C Hamano │4.6k│ │ └─► [PATCH v3 04/12] unpack_object_header(): make it public
. │21-May│ Junio C Hamano │5.7k│ │ └─► [PATCH v3 05/12] write_entry(): separate two helper functions out
. │21-May│ Junio C Hamano │9.4k│ │ └─► [PATCH v3 06/12] streaming: a new API to read from the object store
. │21-May│ Junio C Hamano │8.0k│ │ └─► [PATCH v3 07/12] streaming_write_entry(): use streaming API in write_entry()
. │21-May│ Junio C Hamano │4.7k│ │ └─► [PATCH v3 09/12] streaming_write_entry(): support files with holes
. │21-May│ Junio C Hamano │3.7k│ │ └─► [PATCH v3 08/12] convert: CRLF_INPUT is a no-op in the output codepath
. │21-May│ Junio C Hamano │6.5k│ │ └─► [PATCH v3 10/12] streaming: read non-delta incrementally from a pack
. │21-May│ Junio C Hamano │5.5k│ │ └─► [PATCH v3 11/12] sha1_file.c: expose helpers to read loose objects
. │21-May│ Junio C Hamano │5.8k│ │ └─► [PATCH v3 12/12] streaming: read loose objects incrementally
Does anyone else see this and is it a bug? Thanks.
Leo
next reply other threads:[~2011-05-21 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 7:13 Leo [this message]
2011-05-30 18:12 ` Lars Magne Ingebrigtsen
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=m18vu0y1a3.fsf@th041140.ip.tsinghua.edu.cn \
--to=sdl.web@gmail.com \
--cc=ding@gnus.org \
/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;
as well as URLs for NNTP newsgroup(s).