From: Mark Maule <maule@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: change to the ia64 GIT trees
Date: Thu, 18 Aug 2005 13:14:15 +0000 [thread overview]
Message-ID: <20050818131415.GJ4191@sgi.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F042945E9@scsmsx401.amr.corp.intel.com>
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
next prev parent reply other threads:[~2005-08-18 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2005-08-25 13:16 ` Martin Hicks
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=20050818131415.GJ4191@sgi.com \
--to=maule@sgi.com \
--cc=linux-ia64@vger.kernel.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