From: Pete Zaitcev <zaitcev@redhat.com>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: linux-kernel@vger.kernel.org, Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: Juju
Date: Mon, 29 Jan 2007 12:22:44 -0800 [thread overview]
Message-ID: <20070129122244.54fbcdfe.zaitcev@redhat.com> (raw)
In-Reply-To: <45BE50B8.2080001@redhat.com>
On Mon, 29 Jan 2007 14:53:28 -0500, Kristian Høgsberg <krh@redhat.com> wrote:
> >> git://people.freedesktop.org/~krh/linux-2.6
> >
> > This seems to have disappeared. Was it moved or dropped?
>
> No, it's still there, and I just did a git clone on it. How does it fail for
> you?
Oh never mind, sorry. It said "Already up-to-date", but since HTTP
does not show it, I assumed it's not there.
> In any case, you're probably better of pulling from Stefans kernel.org tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
>
> since that's where new work is going to show up. I'm still trying to figure
> out a good workflow for this, but if all patches are going to through
> linux1394-devel, there's not much point in me publishing a branch in the
> freedesktop.org repo, if the patches are going to be edited/tweaked and the
> committed to Stefans repo.
I see, thanks.
-- Pete
prev parent reply other threads:[~2007-01-29 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 6:37 Juju Pete Zaitcev
2007-01-25 17:13 ` Juju Stefan Richter
2007-01-25 21:18 ` Juju Kristian Høgsberg
2007-01-25 23:38 ` Juju Pete Zaitcev
2007-01-26 2:35 ` Juju Stefan Richter
2007-01-26 4:01 ` Juju Kristian Høgsberg
2007-01-26 11:30 ` Juju Stefan Richter
2007-01-26 4:47 ` Juju Pete Zaitcev
2007-01-26 10:53 ` Juju Stefan Richter
2007-01-26 6:47 ` Juju Greg KH
2007-01-26 19:51 ` Juju Kristian Høgsberg
2007-01-29 0:13 ` Juju Pete Zaitcev
2007-01-29 19:53 ` Juju Kristian Høgsberg
2007-01-29 20:22 ` Pete Zaitcev [this message]
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=20070129122244.54fbcdfe.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.