postgres-xc-general Mailing List for Postgres-XC

Appreciate for very nice and interesting topics.
----------
Koichi Suzuki


2013/2/13 Zenaan Harkness <ze...@fr...>:
> [SOLVED]
>
> On 2/13/13, Michael Paquier <mic...@gm...> wrote:
>> On Wed, Feb 13, 2013 at 1:28 PM, Zenaan Harkness <ze...@fr...> wrote:
>>
>>> On 2/13/13, Zenaan Harkness <ze...@fr...> wrote:
>>> > # this resulted in only 8.6MiB download just now,
>>> > # on an up-to-date pg.git repo.
>>
>> This quantity of data looks correct, half of it being due to the data in
>> doc-xc/.
>>
>> $ git remote set-branches --add master pgxc/master
>>> fatal: No such remote 'master'
>>
>> I am not a GIT specialist, but in order to get all the branches, do only
>> that:
>> git remote add -f pgxc git://
>> postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
>>
>> You will be able to see all the remote branches available with "git branch
>> -a"
>
> Bingo! Thank you very much. I ran git remote rm pgxc (rm my previous
> remote attempt), then ran your command.
> It appears that for some reason --tags option (possibly when combined
> with -m) causes a problem with fetching remote branches.
>
> Much appreciated,
> Zenaan
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

[SOLVED]

On 2/13/13, Michael Paquier <mic...@gm...> wrote:
> On Wed, Feb 13, 2013 at 1:28 PM, Zenaan Harkness <ze...@fr...> wrote:
>
>> On 2/13/13, Zenaan Harkness <ze...@fr...> wrote:
>> > # this resulted in only 8.6MiB download just now,
>> > # on an up-to-date pg.git repo.
>
> This quantity of data looks correct, half of it being due to the data in
> doc-xc/.
>
> $ git remote set-branches --add master pgxc/master
>> fatal: No such remote 'master'
>
> I am not a GIT specialist, but in order to get all the branches, do only
> that:
> git remote add -f pgxc git://
> postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
>
> You will be able to see all the remote branches available with "git branch
> -a"

Bingo! Thank you very much. I ran git remote rm pgxc (rm my previous
remote attempt), then ran your command.
It appears that for some reason --tags option (possibly when combined
with -m) causes a problem with fetching remote branches.

Much appreciated,
Zenaan

On Wed, Feb 13, 2013 at 1:28 PM, Zenaan Harkness <ze...@fr...> wrote:

> On 2/13/13, Zenaan Harkness <ze...@fr...> wrote:
> > # this resulted in only 8.6MiB download just now,
> > # on an up-to-date pg.git repo.
>
This quantity of data looks correct, half of it being due to the data in
doc-xc/.

$ git remote set-branches --add master pgxc/master
> fatal: No such remote 'master'
>

I am not a GIT specialist, but in order to get all the branches, do only
that:
git remote add -f pgxc git://
postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc

You will be able to see all the remote branches available with "git branch
-a"
In this case, remote branches will be listed as remotes/pgxc/master,
remotes/pgxc/REL1_0_STABLE, or whatever.

Then checkout a branch, here master, with that:
git branch --track pgxc-master pgxc/master
git checkout pgxc-master
This will create a branch called pgxc-master set to track the remote PGXC
master branch when doing a git pull on this branch. Replace pgxc-master by
the name you wish.
-- 
Michael

On 2/13/13, Zenaan Harkness <ze...@fr...> wrote:
> Here's what I just tried:
>
> cd postgresql.git/
> git remote add -f --tags -m master pgxc
> git://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc

Please note, the above two lines should be one, forgot to manually format sorry.

> # this resulted in only 8.6MiB download just now,
> # on an up-to-date pg.git repo.
>
> #view results:
> git remote -v
> git branch -a
>
> In my case, remotes/pgxc/HEAD is the only pgxc 'branch' so it appears
> I'm not quite doing something right. Looking at the repo summary page
> at:
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
> suggests that there are a number of 'heads' which I assume are branches.
> My ~/.gitconfig only has user name and email, so nothing there should
> be stopping the branches from being downloaded.
>
> I guess I'm missing something in my command above. From my reading of
> man git-remote it should do the trick...
>
> Anyone know what's wrong with it?

I just tried the following:

$ git remote set-branches --add master pgxc/master
fatal: No such remote 'master'

??

Here's what I just tried:

cd postgresql.git/
git remote add -f --tags -m master pgxc
git://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc
# this resulted in only 8.6MiB download just now,
# on an up-to-date pg.git repo.

#view results:
git remote -v
git branch -a

In my case, remotes/pgxc/HEAD is the only pgxc 'branch' so it appears
I'm not quite doing something right. Looking at the repo summary page
at:
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
suggests that there are a number of 'heads' which I assume are branches.
My ~/.gitconfig only has user name and email, so nothing there should
be stopping the branches from being downloaded.

I guess I'm missing something in my command above. From my reading of
man git-remote it should do the trick...

Anyone know what's wrong with it?

TIA
Zenaan

fyi..

---------- Forwarded message ----------
From: Michael Paquier
Date: Wed, 13 Feb 2013 12:59:54 +0900

On Tue, Feb 12, 2013 at 2:36 PM, Zenaan Harkness <ze...@fr...> wrote:

> Does somone know the object overlap likely between pg and pgxc
> repositories?
>
> I ask because I could just git clone pgxc, or I could add a remote for
> pgxc to my pg git clone, and make sure the branches are added, and
> fetch that remote.
> And in this way, common files/ objects are properly shared in one
> repo, rather than duplicated.
>
PG and PGXC share 99.9% of a common commit history, so yes simply adding a
remote to PGXC in your existing PG folder is good. This is how I do for my
own dev, and I believe that most of the people in this project do the same.
Doing that is particularly helpful when you want to merge PG code directly
in XC or when you need to have a look at the code diffs between both
projects.
-- 
Michael

---------- Forwarded message ----------
From: Koichi Suzuki <koi...@gm...>
Date: Wed, 13 Feb 2013 10:49:51 +0900
Subject: Re: [GENERAL] cloning postgres-xc
Cc: pgs...@po...

Yes, this ML is not a right place to discuss this.

Could you raise this issue at postgres-xc-general ML?

Regards;
----------
Koichi Suzuki


2013/2/12 Pavan Deolasee <pav...@gm...>:
> This may not be the best place to ask these questions and you could
> have considered using postgres-xc-general mailing list from the
> Postgres-XC project site. Anyways, see my comments below.
>
> On Tue, Feb 12, 2013 at 11:06 AM, Zenaan Harkness <ze...@fr...> wrote:
>> Does somone know the object overlap likely between pg and pgxc repositories?
>
> There is quite a lot overlap. Even though Postgres-XC has changed many
> files and added many other, there is still plenty of common code.
>
>> I ask because I could just git clone pgxc, or I could add a remote for
>> pgxc to my pg git clone, and make sure the branches are added, and
>> fetch that remote.
>> And in this way, common files/ objects are properly shared in one
>> repo, rather than duplicated.
>>
>> Thoughts?
>>
>
> ISTM that's the right way, especially if you're interested in keeping
> PG code as well. This way, you will avoid a lot of duplicates and can
> also quickly do a "git diff" between files of these two projects. I
> find that very convenient at times.
>
> Thanks,
> Pavan
>
> --
> Pavan Deolasee
> http://www.linkedin.com/in/pavandeolasee
>
>
> --
> Sent via pgsql-general mailing list (pgs...@po...)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general