From: Jon Loeliger <jdl@freescale.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Carl Baldwin <cnb@fc.hp.com>, Git List <git@vger.kernel.org>
Subject: Re: [Question] Fetching a new branch from remote
Date: Thu, 01 Dec 2005 14:40:56 -0600 [thread overview]
Message-ID: <1133469656.30767.76.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <7vk6eoinqa.fsf@assigned-by-dhcp.cox.net>
On Thu, 2005-12-01 at 14:09, Junio C Hamano wrote:
>
> I just found out that the documentation for '-f' flag is simply
> missing. I'd propose to add the following. Thanks for noticing.
Hmm. Apologies. I had mentioned it back here, but
didn't know what it did and so didn't document it:
From: Jon Loeliger <jdl@freescale.com>
To: git@vger.kernel.org
Subject: [PATCH] Add --tags documentation, scraped from JC mail.
Date: Mon, 7 Nov 2005 07:03:30 -0700
Signed-off-by: Jon Loeliger <jdl@freescale.com>
---
Thin territory here for me. Feel free to alter if not right! :-)
Also notice the lonely --force option still...
next prev parent reply other threads:[~2005-12-01 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 16:33 [Question] Fetching a new branch from remote Carl Baldwin
2005-12-01 20:09 ` Junio C Hamano
2005-12-01 20:40 ` Jon Loeliger [this message]
2005-12-02 15:50 ` Carl Baldwin
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=1133469656.30767.76.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=cnb@fc.hp.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).