linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: dougg@torque.net, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org, russb@emc.com
Subject: Re: [PATCH 0/3] libata: scsi error handling, encore
Date: Wed, 19 Oct 2005 12:47:05 +0900	[thread overview]
Message-ID: <4355C1B9.3080700@gmail.com> (raw)
In-Reply-To: <435563D0.7050502@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
> 
>> $ cat ~/bin/git-sync.sh
>> #!/bin/sh
>>
>> if [ ! -r .git/origin ]; then
>>         echo "not in git repo" 2>&1
>>         exit 1
>> fi
>>
>> rsync -avz --ignore-existing $(cat .git/origin)/ .git/
>> rsync -avz $(cat .git/origin)/refs/ .git/refs/
>>
>>  After syncing, you need to do 'git-read-tree -m upstream' 
>> 'git-checkout-cache -q -f -u -a'
> 
> 
> 
> In the fast-moving world of git, this is a bit outdated.  You should use
> 
>     git checkout -f upstream
> 
> to check out a specific branch.
> 

  Oh.. there was the '-f' switch.  I always hit 'xxx changed' message 
without the option and have gotten into the habit of using 
read-tree/checkout-cache after a while.  Thanks for the tip.

-- 
tejun

  reply	other threads:[~2005-10-19  3:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09 12:23 [PATCH 0/3] libata: scsi error handling, encore Douglas Gilbert
2005-10-09 13:23 ` Jeff Garzik
2005-10-09 17:30   ` Luben Tuikov
2005-10-09 17:43     ` Jeff Garzik
2005-10-15  2:30   ` Douglas Gilbert
2005-10-15  2:34     ` Jeff Garzik
2005-10-15  3:46       ` Douglas Gilbert
2005-10-15  3:54         ` Tejun Heo
2005-10-15  3:55           ` Tejun Heo
2005-10-18 21:06           ` Jeff Garzik
2005-10-19  3:47             ` Tejun Heo [this message]
2005-10-15  5:08       ` Albert Lee

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=4355C1B9.3080700@gmail.com \
    --to=htejun@gmail.com \
    --cc=dougg@torque.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=russb@emc.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).