Re: Converting from anonymous git clone to eponymous

[Simos Xenitellis <simos lists googlemail com>]

I did some more testing and I have put up a temporary page at
http://live.gnome.org/SimosXenitellis/GitConvertAnonymousToEponymous

The gist is that if you have an anonymous clone, you can convert to
eponymous with the following four commands,

1. git remote rm origin
2. git remote add origin -f -m master
ssh://MYUSERNAME git gnome org/git/MODULENAME/
3. git config branch.master.remote origin
4. git config branch.master.merge refs/heads/master

Simos

On Thu, May 7, 2009 at 2:41 AM, Simos Xenitellis
<simos lists googlemail com> wrote:
> I am trying to find what is the best way to convert an anonymous clone
> to a non-anonymous (eponymous?) clone. I could not locate any
> definitive information by searching,
> which is probably due to not searching with the correct keywords.
>
> Are there any comments to the following?
>
> $ git clone git://git.gnome.org/git/eog
> ...
> $ cd eog
> $ git remote rm origin
> $ git remote add -f -m master origin ssh://MYUSERNAME git gnome org/git/eog/
> Updating origin
> From ssh://simos git gnome org/git/eog
>  * [new branch]      EOG_2_12_1 -> origin/EOG_2_12_1
>  * [new branch]      GCONF_BRANCH2 -> origin/GCONF_BRANCH2
>  * [new branch]      GNOME_2_12_BRANCHPOINT -> origin/GNOME_2_12_BRANCHPOINT
>  * [new branch]      GNOME_2_PORT -> origin/GNOME_2_PORT
>  * [new branch]      eog-0-6    -> origin/eog-0-6
>  * [new branch]      eog-for-gnome-1-4 -> origin/eog-for-gnome-1-4
>  * [new branch]      eog-ng     -> origin/eog-ng
>  * [new branch]      experimental-job-mgr -> origin/experimental-job-mgr
>  * [new branch]      gnome-2-0  -> origin/gnome-2-0
>  * [new branch]      gnome-2-10 -> origin/gnome-2-10
>  * [new branch]      gnome-2-12 -> origin/gnome-2-12
>  * [new branch]      gnome-2-14 -> origin/gnome-2-14
>  * [new branch]      gnome-2-16 -> origin/gnome-2-16
>  * [new branch]      gnome-2-18 -> origin/gnome-2-18
>  * [new branch]      gnome-2-18_svn3671 -> origin/gnome-2-18_svn3671
>  * [new branch]      gnome-2-2  -> origin/gnome-2-2
>  * [new branch]      gnome-2-20 -> origin/gnome-2-20
>  * [new branch]      gnome-2-22 -> origin/gnome-2-22
>  * [new branch]      gnome-2-24 -> origin/gnome-2-24
>  * [new branch]      gnome-2-26 -> origin/gnome-2-26
>  * [new branch]      gnome-2-4  -> origin/gnome-2-4
>  * [new branch]      gnome-2-6  -> origin/gnome-2-6
>  * [new branch]      gnome-2-8  -> origin/gnome-2-8
>  * [new branch]      master     -> origin/master
> $ git pull --rebase
> Current branch master is up to date.
> $ git remote show origin
> * remote origin
>  URL: ssh://MYUSERNAME git gnome org/git/eog/
>  Tracked remote branch
>    master
> $ _
>
> An eponymous clone looks like
>
> $ git remote show origin
> * remote origin
>  URL: ssh://MYUSERNAME git gnome org/git/eog
>  Remote branch merged with 'git pull' while on branch master
>    master
>  Tracked remote branches
>    EOG_2_12_1
>    GCONF_BRANCH2
>    GNOME_2_12_BRANCHPOINT
>    GNOME_2_PORT
>    eog-0-6
>    eog-for-gnome-1-4
>    eog-ng
>    experimental-job-mgr
>    gnome-2-0
>    gnome-2-10
>    gnome-2-12
>    gnome-2-14
>    gnome-2-16
>    gnome-2-18
>    gnome-2-18_svn3671
>    gnome-2-2
>    gnome-2-20
>    gnome-2-22
>    gnome-2-24
>    gnome-2-26
>    gnome-2-4
>    gnome-2-6
>    gnome-2-8
>    master
> $ _
>
> The issue I have at the moment is that
>
> git pull --rebase
>
> does not work unless I specify  'git pull --rebase origin master'. How
> do I set these values by default?
>
> Simos
>