On Wed, Jun 24, 2009 at 9:32 AM, David Given<[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andrew Dennison wrote:
> [...]
>> The tree is hosted here:
>>
>> http://github.com/AndrewD/prex/tree
> [...]
>> I'm happy to answer question on how to do some basics with git (it is
>> a fantastic tool) and also to help with the specific task of migrating
>> your changes to the latest version.
>
> I've used git some, but can't say I like it much --- too much experience
> with SVN, I think (from what I can tell, each operation in my standard
> SVN workflow takes two or three steps in git. *Obscure* steps). But it
> is most likely the best tool for this job.

Git has got much cleaner over time. The first versions in 2005 were
very raw but I was forced to use it for Linux kernel work. Now I think
it is fantastic and avoid SVN as much as possible :)

> Which brings me to my point:
>
> $ git clone git://github.com/AndrewD/prex.git
> Initialized empty Git repository in /.user/home/dg/src/prex/.git/
> remote: Counting objects: 2870, done.
> remote: Compressing objects: 100% (1146/1146), done.
> remote: Total 2870 (delta 1606), reused 2870 (delta 1606)
> Receiving objects: 100% (2870/2870), 1.48 MiB | 472 KiB/s, done.
> Resolving deltas: 100% (1606/1606), done.
> warning: remote HEAD refers to nonexistent ref, unable to checkout.
>
> What am I doing wrong here?

Oops. This is because I broke convention and haven't pushed up a
"master" branch yet. This fixes it:

$ cd prex
$ git checkout -b master origin/prex
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of origin/prex.
Branch master set up to track remote branch refs/remotes/origin/prex.
Already on "master"
$ git status
# On branch master
nothing to commit (working directory clean)
$

Andrew

------------------------------------------------------------------------------
_______________________________________________
Prex-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/prex-devel

Reply via email to