* linux-next: md tree not fetchable
@ 2008-08-06 3:17 Stephen Rothwell
2008-08-06 3:44 ` NeilBrown
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2008-08-06 3:17 UTC (permalink / raw)
To: Neil Brown; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Hi Neil,
I could not fetch the md and md-current trees (git://neil.brown.name/md)
today. I got this error:
fatal: The remote end hung up unexpectedly
I will use what I had from yesterday.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: md tree not fetchable
2008-08-06 3:17 linux-next: md tree not fetchable Stephen Rothwell
@ 2008-08-06 3:44 ` NeilBrown
2008-08-06 4:25 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: NeilBrown @ 2008-08-06 3:44 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next
On Wed, August 6, 2008 1:17 pm, Stephen Rothwell wrote:
> Hi Neil,
>
> I could not fetch the md and md-current trees (git://neil.brown.name/md)
> today. I got this error:
>
> fatal: The remote end hung up unexpectedly
That's what you get for running "apt-get upgrade" and not testing things
:-)
Fixed now.
>
> I will use what I had from yesterday.
Ok.
BTW, there is only the one tree that you need to pull: "for-next".
I think the other one (md-current??) was for-linus. That will
always be included in for-next so does not need to be pulled separately.
Thanks,
NeilBrown
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: md tree not fetchable
2008-08-06 3:44 ` NeilBrown
@ 2008-08-06 4:25 ` Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2008-08-06 4:25 UTC (permalink / raw)
To: NeilBrown; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Hi Neil,
On Wed, 6 Aug 2008 13:44:56 +1000 (EST) "NeilBrown" <neilb@suse•de> wrote:
>
> That's what you get for running "apt-get upgrade" and not testing things
> :-)
>
> Fixed now.
Thanks.
> BTW, there is only the one tree that you need to pull: "for-next".
> I think the other one (md-current??) was for-linus. That will
> always be included in for-next so does not need to be pulled separately.
I like to fetch them separately because I merge the for-linus stuff early
and then if there is a severe problem with the for-next part, I only have
to drop that and I still get the benefit of any bug fixes in the
for-linus part. Also, later in the cycle (rc7 or 8 or so) I stop doing
separate builds for the -current tree merges on the (hopefully accurate)
assumption that bugs fixes that Linus has been asked to take will not
cause any problems (and actually may solve some on Linus' tree).
That said, I do like the fact the the for-next part is always a superset
of the for-linus part.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-06 4:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-06 3:17 linux-next: md tree not fetchable Stephen Rothwell
2008-08-06 3:44 ` NeilBrown
2008-08-06 4:25 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox