public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Rong Chen <rong.a.chen@intel.com>
Cc: kbuild@lists.01.org, Kefeng Wang <wangkefeng.wang@huawei.com>,
	kbuild-all@lists.01.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [PATCH next 2/3] debugfs: introduce debugfs_create_single[,_data]
Date: Tue, 3 Dec 2019 12:32:41 +0300	[thread overview]
Message-ID: <20191203092643.GD1787@kadam> (raw)
In-Reply-To: <06d63c3c-bab5-c19e-a51d-ac7c1ed0a80c@intel.com>

On Tue, Dec 03, 2019 at 05:02:54PM +0800, Rong Chen wrote:
> 
> 
> On 12/3/19 4:38 PM, Dan Carpenter wrote:
> > [ How do I fetch 0day git branchs?
> >    git fetch https://github.com/0day-ci/linux/commits/Kefeng-Wang/debugfs-introduce-debugfs_create_single-seq-_data/20191129-173440
> >    doesn't work. - dan ]
> 
> Hi Dan,
> 
> I can fetch it by the following steps:
> 
> nfs@shao2-debian:~/linux$ git remote add 0day-linux-review
> https://github.com/0day-ci/linux.git
> nfs@shao2-debian:~/linux$ git fetch --no-tags 0day-linux-review
> Kefeng-Wang/debugfs-introduce-debugfs_create_single-seq-_data/20191129-173440
> 
> remote: Enumerating objects: 25261, done.
> remote: Counting objects: 100% (25261/25261), done.
> remote: Total 33246 (delta 25260), reused 25260 (delta 25260), pack-reused
> 7985
> Receiving objects: 100% (33246/33246), 12.03 MiB | 1.05 MiB/s, done.
> Resolving deltas: 100% (28148/28148), completed with 6149 local objects.
> From https://github.com/0day-ci/linux
>  * branch
> Kefeng-Wang/debugfs-introduce-debugfs_create_single-seq-_data/20191129-173440
> -> FETCH_HEAD
>  * [new branch]
> Kefeng-Wang/debugfs-introduce-debugfs_create_single-seq-_data/20191129-173440
> -> 0day-linux-review/Kefeng-Wang/debugfs-introduce-debugfs_create_single-seq-_data/20191129-173440
> 

Tracking a remote is unworkably slow on my system.  It's way better to
try fetch a specific branch if possible.

regards,
dan carpenter


  reply	other threads:[~2019-12-03  9:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  9:27 [PATCH next 0/3] debugfs: introduce debugfs_create_single/seq[,_data] Kefeng Wang
2019-11-29  9:27 ` [PATCH next 1/3] debugfs: Provide debugfs_[set|clear|test]_lowest_bit() Kefeng Wang
2019-11-29  9:27 ` [PATCH next 2/3] debugfs: introduce debugfs_create_single[,_data] Kefeng Wang
2019-12-03  8:38   ` Dan Carpenter
2019-12-03  9:02     ` [kbuild-all] " Rong Chen
2019-12-03  9:32       ` Dan Carpenter [this message]
2019-11-29  9:27 ` [PATCH next 3/3] debugfs: introduce debugfs_create_seq[,_data] Kefeng Wang
2019-11-29 14:22   ` Greg KH
2019-11-29 15:03     ` Kefeng Wang
2019-11-29 22:16       ` Greg KH
2019-11-29 14:21 ` [PATCH next 0/3] debugfs: introduce debugfs_create_single/seq[,_data] Greg KH
2019-11-29 15:16   ` Kefeng Wang
2019-11-29 22:19     ` Greg KH
2019-11-29 22:23       ` Greg KH

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=20191203092643.GD1787@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=kbuild@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rong.a.chen@intel.com \
    --cc=wangkefeng.wang@huawei.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