All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [git pull] jfs update
Date: Wed, 04 May 2005 17:05:24 -0500	[thread overview]
Message-ID: <1115244324.8279.72.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0505041437060.2328@ppc970.osdl.org>

cc'ing the git mailing list, dropping linux-kernel

On Wed, 2005-05-04 at 14:37 -0700, Linus Torvalds wrote:
> 
> On Wed, 4 May 2005, Dave Kleikamp wrote:
> >
> > I think I've got this set up right.  I have created a HEAD-for-linus and
> > HEAD-for-mm in the same git repo.
> 
> Ok, my scripts don't handle that very well yet (they just want HEAD), but 
> that was easy enough to hack around. I'll be able to work with that 
> format.

After looking at the documentation and playing around, I'm wondering if
I should instead have created jfs-2.6.git/refs/heads/for-linus.  Then
the url would be:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git#for-linus

I think this currently works.  Which would be the preferred format?

> 
> > Please pull from
> > 
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git/HEAD-for-linus
> 
> Pulled, and pushed out.
> 
> 		Linus
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2005-05-04 21:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 20:47 [git pull] jfs update Dave Kleikamp
2005-05-04 21:37 ` Linus Torvalds
2005-05-04 22:05   ` Dave Kleikamp [this message]
2005-05-05 18:16   ` Jeff Garzik
2005-05-05 18:22     ` Linus Torvalds
2005-05-05 18:51       ` Dave Kleikamp
2005-05-05 19:39         ` Andrew Morton
2005-05-06 19:13           ` Dave Kleikamp
  -- strict thread matches above, loose matches on Subject: below --
2005-06-20 16:18 Dave Kleikamp
2005-07-13 14:41 Dave Kleikamp
2005-07-27 18:05 Dave Kleikamp
2005-07-27 23:43 ` Linus Torvalds
2005-08-04 21:07 Dave Kleikamp
2005-10-28 19:12 Dave Kleikamp
2005-11-09 21:40 Dave Kleikamp
2006-03-14 18:47 Dave Kleikamp
2006-03-14 19:33 ` Linus Torvalds
2006-03-20 14:57 Dave Kleikamp
2006-05-24 13:10 Dave Kleikamp
2006-07-06 14:20 Dave Kleikamp
2006-07-14  1:45 Dave Kleikamp
2006-08-03 14:37 Dave Kleikamp
2006-09-25 13:04 Dave Kleikamp
2006-10-02 15:16 Dave Kleikamp
2006-10-02 15:31 ` Linus Torvalds
2006-10-02 15:41   ` Dave Kleikamp
2006-10-02 16:21     ` Al Viro
2006-10-23 12:53 Dave Kleikamp
2006-11-02 14:23 Dave Kleikamp
2006-11-04  3:07 Dave Kleikamp
2006-12-12 15:16 Dave Kleikamp
2007-02-07 13:35 Dave Kleikamp
2007-02-14 23:08 Dave Kleikamp
2007-04-28 13:20 Dave Kleikamp
2007-05-08 14:51 Dave Kleikamp
2007-07-09 19:34 Dave Kleikamp
2007-10-10 13:35 shaggy
2008-01-25 19:27 shaggy
2008-02-07 21:02 shaggy
2008-04-17 18:36 shaggy
2008-07-14 16:48 shaggy
2008-12-29 16:01 shaggy
2009-03-25 12:43 shaggy
2009-06-11 16:58 [GIT PULL] " shaggy
2009-06-16 19:14 shaggy
2009-07-23 18:27 shaggy
2010-04-21 12:42 shaggy
2011-07-27 14:55 Dave Kleikamp

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=1115244324.8279.72.camel@localhost \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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 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.