From: Tejun Heo <htejun@gmail.com>
To: dougg@torque.net
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
russb@emc.com
Subject: Re: [PATCH 0/3] libata: scsi error handling, encore
Date: Sat, 15 Oct 2005 12:54:07 +0900 [thread overview]
Message-ID: <43507D5F.2050407@gmail.com> (raw)
In-Reply-To: <43507BA7.6090406@torque.net>
Douglas Gilbert wrote:
> Jeff Garzik wrote:
>
>>Douglas Gilbert wrote:
>>
>>
>>>Six days have passed and "git pull ..../libata-dev" still
>>>does not reflect these changes. Am I doing something
>>>wrong? Should I wait before submitting more changes?
>>
>>
>>Your changes are committed to the 'upstream' branch. Maybe you need to do
>> git pull $url upstream
>
>
> Jeff,
> Thanks, indeed I do. Obviously the fact the 'upstream'
> was the active branch in the destination directory was
> not sufficient. So do I need to do both
> 'git pull $url' and 'git pull $url upstream' or is
> the latter sufficient?
>
> "git" does seems an appropriate name :-)
>
> Doug Gilbert
>
Hi, Doug,
I use the following script.
$ 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'
--
tejun
next prev parent reply other threads:[~2005-10-15 3:54 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 [this message]
2005-10-15 3:55 ` Tejun Heo
2005-10-18 21:06 ` Jeff Garzik
2005-10-19 3:47 ` Tejun Heo
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=43507D5F.2050407@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).