mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: jkacur <jkacur@gmail.com>
Cc: akpm@linux-foundation.org, Jan Engelhardt <jengelh@medozas.de>,
	Andy Whitcroft <apw@shadowen.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Make the git URL match usage
Date: Wed, 16 Jul 2008 16:31:08 +0300	[thread overview]
Message-ID: <20080716133108.GC25557@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <200807161500.08500.jkacur@gmail.com>

On Wed, Jul 16, 2008 at 03:00:08PM +0200, jkacur wrote:
> This time, in order to test that the URL was correct, I started a git clone
> (and broke it off of course) on EVERY SINGLE git URL listed in the
> MAINTAINERS file, even the ones that I didn't have to modify.

Thanks for doing this work!

> I believe that this patch is ready to be ACKed and applied, however
> I made some observations that I will follow up on: Here is a summary.

An alternative solution would be to drop the trees from MAINTAINERS and 
instead point to
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=blob;f=Next/Trees 
which is always kept up-to-date.

It does not completely match what's currently in MAINTAINERS, but as 
you've obsserved the information in MAINTAINERS is quite stale.

> 1. Why is the testing and release tree the same?
> HARDWARE MONITORING
> P:	Mark M. Hoffman
> M:	mhoffman@lightlink.com
> L:	lm-sensors@lm-sensors.org
> W:	http://www.lm-sensors.org/
> T:	git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git testing
> T:	git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git release
> S:	Maintained

These are not different trees, "testing" and "release" are branches of 
this tree.

> 2. Required me to change powerpc.git to powerpc-4xx.git
> P:	Josh Boyer
> M:	jwboyer@linux.vnet.ibm.com
> P:	Matt Porter
> M:	mporter@kernel.crashing.org
> W:	http://www.penguinppc.org/
> L:	linuxppc-dev@ozlabs.org
> T:	git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git
> S:	Maintained

That's not the correct tree, please ask the powerpc maintainers.

> 3. This one seems to require password authentication to fetch, howcome?
> MIPS
> P:	Ralf Baechle
> M:	ralf@linux-mips.org
> W:	http://www.linux-mips.org/
> L:	linux-mips@linux-mips.org
> T:	git www.linux-mips.org:/pub/scm/linux.git
> S:	Supported

That's most likely git://git.linux-mips.org/pub/scm/linux

Please ask the maintainer.

> 4. The following 3 drivers are all maintained by the same person
> in the same git repository, but fail when I attempt git clone
> 
> ADM8211 WIRELESS DRIVER
> P:	Michael Wu
> M:	flamingice@sourmilk.net
> L:	linux-wireless@vger.kernel.org
> W:	http://linuxwireless.org/
> T:	git://git.kernel.org/pub/scm/linux/kernel/git/mwu/mac80211-drivers.git
> S:	Maintained
>...
> The failure looks like this
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/mwu/mac80211-drivers.git
> Initialized empty Git repository in /home/jkacur/git-trees/mac80211-drivers/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.kernel.org/pub/scm/linux/kernel/git/mwu/mac80211-drivers.git' failed.
>...

http://git.kernel.org shows all available trees at git.kernel.org and 
their contents.

More interesting is that there is no recent contents, which makes 
listing the trees anyway pointless.

> Finally, more a curiosity than anything, the following 3 repositories do NOT end in .git
> but this does not seem to be a problem either.
> 
> grep git:// MAINTAINERS | grep -v "\.git"
> T:      git://git.qlogic.com/ipath-linux-2.6
> T:      git://opensource.wolfsonmicro.com/linux-2.6-asoc
> T:      git://opensource.wolfsonmicro.com/linux-2.6-touch
>...

With the default git-daemon configuration it doesn't matter whether or 
not you specify a .git postfix.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-07-16 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 13:00 jkacur
2008-07-16 13:31 ` Adrian Bunk [this message]
2008-07-16 13:41   ` Mark Brown
2008-07-16 15:16     ` Jan Engelhardt
2008-07-16 13:53   ` Grant Likely
2008-07-16 13:54     ` Josh Boyer
     [not found] <aQ9CN-4cK-11@gated-at.bofh.it>
2008-07-16  8:54 ` Bodo Eggert
2008-07-16 10:06   ` Jan Engelhardt
2008-07-16 10:28     ` John Kacur
2008-07-16 10:58     ` John Kacur
  -- strict thread matches above, loose matches on Subject: below --
2008-07-16  8:47 jkacur
2008-07-16 10:21 ` Andy Whitcroft
2008-07-16 10:34   ` John Kacur
2008-07-16 11:43     ` Jan Engelhardt
2008-07-16 12:30       ` John Kacur
2008-07-16  7:19 jkacur
2008-07-16  8:29 ` Jan Engelhardt

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=20080716133108.GC25557@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=jengelh@medozas.de \
    --cc=jkacur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®