From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Yann Dirson <ydirson@altern.org>,
git@vger.kernel.org, Carl Worth <cworth@cworth.org>
Subject: Re: Difficulties in advertising a new branch to git newbies
Date: Tue, 30 Jan 2007 22:40:08 +0100 [thread overview]
Message-ID: <200701302240.09212.jnareb@gmail.com> (raw)
In-Reply-To: <7vwt34xksz.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Yann Dirson <ydirson@altern.org> writes:
>
>> On Tue, Jan 30, 2007 at 10:02:40PM +0100, Jakub Narebski wrote:
>>>> I propose this warning be removed here. Otherwise, I either add text
>>>> to my instructions telling the user to ignore the warning message they
>>>> get, or else I go back to "-b build" and back to all the old problems
>>>> it causes.
>>>
>>> I rather leave warning, but (perhaps around 1.5.1) remove the
>>> instructions. RTFM (err... I'm not sure we have one about detached HEAD).
>>
>> Or provide a "-q" flag to silence the warning ?
>
> Or maybe make "-f" to mean "I know what I am doing, do not
> warn".
Unfortunately "-f" in git-checkout mean "force a re-read of everything."
Besides I'd like to have "-q" option for example for git-cat-file for
gitweb...
> P.S. Jakub, *please* do not break the thread.
I'll try.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-01-30 21:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 20:13 Difficulties in advertising a new branch to git newbies Carl Worth
2007-01-30 21:02 ` Jakub Narebski
2007-01-30 21:25 ` Yann Dirson
2007-01-30 21:31 ` Jakub Narebski
2007-01-30 21:32 ` Junio C Hamano
2007-01-30 21:40 ` Jakub Narebski [this message]
2007-01-30 22:33 ` Matthias Lederhofer
2007-01-30 22:36 ` Matthias Lederhofer
2007-01-30 23:10 ` Jeff King
2007-01-31 1:34 ` Junio C Hamano
2007-01-31 1:51 ` Nicolas Pitre
2007-01-31 3:22 ` Jeff King
2007-01-31 14:59 ` Nicolas Pitre
2007-01-31 17:07 ` Jeff King
2007-01-31 18:59 ` Nicolas Pitre
2007-01-31 22:53 ` Jeff King
2007-01-31 20:20 ` Junio C Hamano
2007-01-31 22:51 ` Theodore Tso
2007-01-31 23:03 ` Junio C Hamano
2007-01-31 23:18 ` Jakub Narebski
2007-01-31 1:48 ` Nicolas Pitre
2007-01-31 0:10 ` Daniel Barkalow
2007-01-31 1:55 ` Nicolas Pitre
2007-01-31 5:09 ` Daniel Barkalow
2007-01-31 14:31 ` Nicolas Pitre
2007-01-31 14:38 ` J. Bruce Fields
2007-01-31 14:53 ` Jakub Narebski
2007-01-31 15:15 ` Nicolas Pitre
2007-01-31 16:25 ` Daniel Barkalow
2007-01-31 18:25 ` Nicolas Pitre
2007-01-31 13:13 ` Guilhem Bonnefille
2007-01-31 16:06 ` Carl Worth
2007-01-31 16:15 ` Johannes Schindelin
2007-01-31 19:27 ` Santi Béjar
2007-01-31 19:50 ` Carl Worth
2007-02-01 0:20 ` Josef Weidendorfer
2007-02-01 9:02 ` Santi Béjar
2007-02-01 4:12 ` Jakub Narebski
2007-02-06 5:51 ` Carl Worth
2007-02-06 6:37 ` Junio C Hamano
2007-02-06 7:25 ` Junio C Hamano
2007-02-06 7:31 ` Jeff King
2007-02-06 18:53 ` Carl Worth
2007-02-06 19:14 ` Junio C Hamano
2007-02-06 19:39 ` Carl Worth
2007-02-06 19:58 ` Jakub Narebski
2007-02-06 7:28 ` Jeff King
2007-02-06 7:46 ` Junio C Hamano
2007-02-06 8:12 ` Jeff King
2007-02-06 15:33 ` Nicolas Pitre
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=200701302240.09212.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ydirson@altern.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).