From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Richard W.M. Jones" <rjones@redhat.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add note about needing to do 'git checkout -f master'.
Date: Tue, 13 Feb 2007 10:09:50 -0800 [thread overview]
Message-ID: <7vps8evsi9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0702131857460.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 13 Feb 2007 18:58:02 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Mon, 12 Feb 2007, Richard W.M. Jones wrote:
>
>> From: Richard Jones <rjones@redhat.com>
>>
>> ---
>> Documentation/git-cvsimport.txt | 6 ++++++
>> 1 files changed, 6 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
>> index f5450de..7b43ed4 100644
>> --- a/Documentation/git-cvsimport.txt
>> +++ b/Documentation/git-cvsimport.txt
>> @@ -138,6 +138,12 @@ If '-v' is specified, the script reports what it is doing.
>> Otherwise, success is indicated the Unix way, i.e. by simply exiting with
>> a zero exit status.
>>
>> +NOTES
>> +-----
>> +If importing for the first time into a directory (-C option),
>> +after the import do 'git checkout -f master' in the new
>> +directory.
>> +
>>
>> Author
>> ------
>> --
>> 1.4.4.2
>
> AFAICT this is no longer necessary in 1.5.0.
I think you are right. I always run cvsimport with -i so I was
confused ;-).
next prev parent reply other threads:[~2007-02-13 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1171302581735-git-send-email->
2007-02-13 17:58 ` [PATCH] Add note about needing to do 'git checkout -f master' Johannes Schindelin
2007-02-13 18:09 ` Junio C Hamano [this message]
2007-02-13 8:18 Richard W.M. Jones
-- strict thread matches above, loose matches on Subject: below --
2007-02-12 17:49 Richard W.M. Jones
2007-02-13 18:06 ` Junio C Hamano
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=7vps8evsi9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=rjones@redhat.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).