From: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Greg KH <greg@kroah.com>,
david@lang.hm, Bryan Donlan <bdonlan@fushizen.net>,
git@vger.kernel.org
Subject: Re: how to track multiple upstreams in one repository
Date: Wed, 21 Jan 2009 18:02:51 +0200 [thread overview]
Message-ID: <8e04b5820901210802y1102cfd0q4a3f8812f357c398@mail.gmail.com> (raw)
In-Reply-To: <20090120120319.GR30710@genesis.frugalware.org>
On Tue, Jan 20, 2009 at 2:03 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Tue, Jan 20, 2009 at 09:29:13AM +0200, "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com> wrote:
>> :) This is something that escaped me... Could you give me the
>> exact git url for this repository? (on kernel.org I'm not able to find
>> it, just the current one...)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git
>
> Have you tried this one?
Ok... I'm ashamed... :) :) This is exactly what (we all) were
looking for... Sorry.
Just one curiosity: is this older (I mean if it was created) than
when 2.6.18 or 19 was released? Because at that time I've searched for
such a repository, didn't found it and hacked the config as I've said
previously...
Ciprian Craciun.
next prev parent reply other threads:[~2009-01-21 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 2:58 how to track multiple upstreams in one repository david
2009-01-19 2:14 ` Bryan Donlan
2009-01-19 3:58 ` david
2009-01-19 7:52 ` Ciprian Dorin, Craciun
2009-01-20 3:34 ` Greg KH
2009-01-20 7:29 ` Ciprian Dorin, Craciun
2009-01-20 12:03 ` Miklos Vajna
2009-01-21 16:02 ` Ciprian Dorin, Craciun [this message]
2009-01-21 16:11 ` Greg KH
2009-01-19 2:18 ` A Large Angry SCM
2009-01-19 16:29 ` Julian Phillips
2009-01-19 21:08 ` david
2009-01-19 20:45 ` Julian Phillips
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=8e04b5820901210802y1102cfd0q4a3f8812f357c398@mail.gmail.com \
--to=ciprian.craciun@gmail.com \
--cc=bdonlan@fushizen.net \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=greg@kroah.com \
--cc=vmiklos@frugalware.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;
as well as URLs for NNTP newsgroup(s).