public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* change to the ia64 GIT trees
@ 2005-08-16 22:00 Luck, Tony
  2005-08-18  3:45 ` Ian Wienand
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: Luck, Tony @ 2005-08-16 22:00 UTC (permalink / raw)
  To: linux-ia64

Now that GIT is smarter, and I'm more aware of what it can do
(and how to make it do it), I'm making a small change to how
I export GIT trees on kernel.org.

Instead of having separate trees for test and release, there
is now just one tree which contains "test" and "release" branches.
[or there will be soon when my deletion of the old test tree
is reflected on the kernel.org mirrors].

You can pull each of the branches separately with:

 $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 test
or
 $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 release

I wrote a "howto" for GIT about using branches as a Linux
subsystem maintainer that was included in the GIT sources
yesterday.  You can read a copy at http://tinyurl.com/d57dc

-Tony

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
@ 2005-08-18  3:45 ` Ian Wienand
  2005-08-18  4:29 ` Andrew Morton
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Ian Wienand @ 2005-08-18  3:45 UTC (permalink / raw)
  To: linux-ia64

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

On Tue, Aug 16, 2005 at 03:00:38PM -0700, Luck, Tony wrote:
> Instead of having separate trees for test and release, there
> is now just one tree which contains "test" and "release" branches.

Does anyone know how one gets to these using cogito?  Or maybe I
should just not use cogito?

$ cg-clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git linux-2.6.git
$ cd linux-2.6.git
$ cg-branch-ls
origin  rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git

I had expected to see the test and release branches there.

> You can pull each of the branches separately with:
> 
>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 test
> or
>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 release

Is that supposed to be linux-2.6.git?
 
Along the same lines, when I look at the web view at

http://www.kernel.org/git/?p=linux/kernel/git/aegl/linux-2.6.git;a=summary

and especially the "tree" view (which I use a bit to see what has
changed in a file) what branch am I looking at there, the test or the
release? 

-i

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
  2005-08-18  3:45 ` Ian Wienand
@ 2005-08-18  4:29 ` Andrew Morton
  2005-08-18  5:05 ` Luck, Tony
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Andrew Morton @ 2005-08-18  4:29 UTC (permalink / raw)
  To: linux-ia64

"Luck, Tony" <tony.luck@intel.com> wrote:
>
> Now that GIT is smarter, and I'm more aware of what it can do
> (and how to make it do it), I'm making a small change to how
> I export GIT trees on kernel.org.
> 
> Instead of having separate trees for test and release, there
> is now just one tree which contains "test" and "release" branches.
> [or there will be soon when my deletion of the old test tree
> is reflected on the kernel.org mirrors].
> 
> You can pull each of the branches separately with:
> 
>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 test
> or
>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 release

Methinks these are supposed to be .../linux-2.6.git, yes?

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
  2005-08-18  3:45 ` Ian Wienand
  2005-08-18  4:29 ` Andrew Morton
@ 2005-08-18  5:05 ` Luck, Tony
  2005-08-18  5:10 ` Luck, Tony
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Luck, Tony @ 2005-08-18  5:05 UTC (permalink / raw)
  To: linux-ia64

>> Instead of having separate trees for test and release, there
>> is now just one tree which contains "test" and "release" branches.
>
>Does anyone know how one gets to these using cogito?  Or maybe I
>should just not use cogito?

I started off using cogito in the early days of GIT, but I didn't
keep up with its development ... so I don't know how to pull these
with cogito.  This might be a case where pure GIT and cogito play
nice together ... so you could try a "git pull" to get each branch
and see what cogito thinks of it.  A git branch is just an extra
file in .git/refs/heads/ with the SHA1 of the head of that branch.

>> You can pull each of the branches separately with:
>> 
>>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 test
>> or
>>  $ git pull rsync://rsync.kernel.org/..../aegl/linux-2.6 release
>
>Is that supposed to be linux-2.6.git?

Doh!  Yes, I can't remember the name of my own GIT tree, isn't that
sad.

>Along the same lines, when I look at the web view at
>
>http://www.kernel.org/git/?p=linux/kernel/git/aegl/linux-2.6.git;a=summ
ary
>
>and especially the "tree" view (which I use a bit to see what has
>changed in a file) what branch am I looking at there, the test or the
>release? 

The ".git/HEAD" symlink in my tree points to the "release" branch, so
that's what gitweb will show by default.

But, if you scroll down to the bottom of the summary page you'll
see links for the test/release branches.  Click on "test" and the
page you get to will have a "tree" link that allows you to browse
the test tree.  You can also browse a historic tree by searching
back to some old commit, and clicking the "tree" you find there.

-Tony


^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
                   ` (2 preceding siblings ...)
  2005-08-18  5:05 ` Luck, Tony
@ 2005-08-18  5:10 ` Luck, Tony
  2005-08-18 13:14 ` Mark Maule
  2005-08-25 13:16 ` Martin Hicks
  5 siblings, 0 replies; 7+ messages in thread
From: Luck, Tony @ 2005-08-18  5:10 UTC (permalink / raw)
  To: linux-ia64


>Methinks these are supposed to be .../linux-2.6.git, yes?

Correct.  See earlier "Doh!"

-Tony

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
                   ` (3 preceding siblings ...)
  2005-08-18  5:10 ` Luck, Tony
@ 2005-08-18 13:14 ` Mark Maule
  2005-08-25 13:16 ` Martin Hicks
  5 siblings, 0 replies; 7+ messages in thread
From: Mark Maule @ 2005-08-18 13:14 UTC (permalink / raw)
  To: linux-ia64

On Wed, Aug 17, 2005 at 10:05:51PM -0700, Luck, Tony wrote:
> >> Instead of having separate trees for test and release, there
> >> is now just one tree which contains "test" and "release" branches.
> >
> >Does anyone know how one gets to these using cogito?  Or maybe I
> >should just not use cogito?
> 
> I started off using cogito in the early days of GIT, but I didn't
> keep up with its development ... so I don't know how to pull these
> with cogito.  This might be a case where pure GIT and cogito play
> nice together ... so you could try a "git pull" to get each branch
> and see what cogito thinks of it.  A git branch is just an extra
> file in .git/refs/heads/ with the SHA1 of the head of that branch.

I'm no git/cogito expert, but the following worked for me to get a test
branch snapshot:

cg-clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#test test

This gets the correct source, but the branch names are misleading to me:

attica$ cg-branch-ls
origin  rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#test

Mark

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: change to the ia64 GIT trees
  2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
                   ` (4 preceding siblings ...)
  2005-08-18 13:14 ` Mark Maule
@ 2005-08-25 13:16 ` Martin Hicks
  5 siblings, 0 replies; 7+ messages in thread
From: Martin Hicks @ 2005-08-25 13:16 UTC (permalink / raw)
  To: linux-ia64


On Thu, Aug 18, 2005 at 08:14:15AM -0500, Mark Maule wrote:
> 
> I'm no git/cogito expert, but the following worked for me to get a test
> branch snapshot:
> 
> cg-clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#test test
> 
> This gets the correct source, but the branch names are misleading to me:
> 
> attica$ cg-branch-ls
> origin  rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#test

Clone the main repository and cg-branch-add the test branch?

mh

-- 
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2005-08-25 13:16 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-16 22:00 change to the ia64 GIT trees Luck, Tony
2005-08-18  3:45 ` Ian Wienand
2005-08-18  4:29 ` Andrew Morton
2005-08-18  5:05 ` Luck, Tony
2005-08-18  5:10 ` Luck, Tony
2005-08-18 13:14 ` Mark Maule
2005-08-25 13:16 ` Martin Hicks

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox