From: Nicolas Pitre <nico@fluxnic.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stephen Boyd <bebarino@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: reword --thin description
Date: Wed, 10 Feb 2010 16:04:57 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002101554200.1681@xanadu.home> (raw)
In-Reply-To: <7vsk98apcr.fsf@alter.siamese.dyndns.org>
On Wed, 10 Feb 2010, Junio C Hamano wrote:
> Nicolas Pitre <nico@fluxnic.net> writes:
>
> > .... But --thin turned
> > out to be re-enabled by default for pushes by mistake on a few occasions
> > when the affected code has been reworked. No idea what state it is now,
> > and I don't think that makes such a difference on the server in the end.
>
> Hmmmm... it's doubly bad that the maintainer does not recall these
> few occasions that mistakes happened.
The default was changed in commit a4503a15af. Seems that today --thin
is on by default again. I don't think we should care that much,
especially as --thin would logically have to be the default when pushing
to a bundle. Obviously leaving it off for push and on for fetch is
creating needless confusion.
Nicolas
next prev parent reply other threads:[~2010-02-10 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 5:14 [PATCH] Documentation: reword --thin description Stephen Boyd
2010-02-10 16:07 ` Nicolas Pitre
2010-02-10 16:52 ` Stephen Boyd
2010-02-10 18:59 ` Junio C Hamano
2010-02-10 21:04 ` Nicolas Pitre [this message]
2010-02-12 8:00 ` [PATCHv2] Documentation: describe --thin more accurately Stephen Boyd
2010-02-12 17:36 ` Junio C Hamano
2010-02-15 19:33 ` [PATCHv3] " Stephen Boyd
2010-02-15 20:44 ` Junio C Hamano
2010-02-18 8:33 ` Stephen Boyd
2010-02-18 9:10 ` [PATCHv4] " Stephen Boyd
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.00.1002101554200.1681@xanadu.home \
--to=nico@fluxnic.net \
--cc=bebarino@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).