linux-kernel - Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 18 Oct 2016 12:08:45 +0800
From:   Shawn Lin <shawn.lin@...k-chips.com>
To:     Jaehoon Chung <jh80.chung@...sung.com>,
        Ulf Hansson <ulf.hansson@...aro.org>, linux-mmc@...r.kernel.org
Cc:     shawn.lin@...k-chips.com, linux-kernel@...r.kernel.org,
        Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

在 2016/10/18 11:52, Jaehoon Chung 写道:
> On 10/18/2016 12:19 PM, Shawn Lin wrote:
>> Hi Ulf,
>>
>> On 2016/10/17 20:54, Ulf Hansson wrote:
>>> Signed-off-by: Ulf Hansson <ulf.hansson@...aro.org>
>>> ---
>>>  MAINTAINERS | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index a009e00..e685724 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -8164,7 +8164,7 @@ F:    include/linux/mfd/
>>>  MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND SDIO SUBSYSTEM
>>>  M:    Ulf Hansson <ulf.hansson@...aro.org>
>>>  L:    linux-mmc@...r.kernel.org
>>> -T:    git git://git.linaro.org/people/ulf.hansson/mmc.git
>>> +T:    git git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git
>>
>> I cannot clone this tree, and I have tried some of my servers, although.
>>
>> remote: Total 5031043 (delta 4225582), reused 5030965 (delta 4225531)
>> Resolving deltas: 100% (4225582/4225582), done.
>> Checking connectivity... done.
>> warning: remote HEAD refers to nonexistent ref, unable to checkout.
>
> you have to checkout to "next"

yep, it does need to assign a HEAD blob after cloning.
But I never did it when cloning other maintainers' tree.

Thanks.

> e.g) git checkout next
>
> Best Regards,
> Jaehoon Chung
>
>>
>> ...then the clone process failed.
>>
>>>  S:    Maintained
>>>  F:    Documentation/devicetree/bindings/mmc/
>>>  F:    drivers/mmc/
>>>
>>
>>
>
>
>
>


-- 
Best Regards
Shawn Lin