Re: [arch-general] Git
On 2013-29-09, Tom Gundersen <teg@jklm.no> wrote:
If we were to use git, we should have one git repository per package, and also provide one repository which includes all the packages as submodules.
Why not use one branch per package and one branch per repository with the packages as submodules instead of a repository for each package? This way all the packages would be in a single repository and could be fetched all at once or one at a time.
On Monday 30 Sep 2013 05:13:57 Sebastian Schwarz wrote:
On 2013-29-09, Tom Gundersen <teg@jklm.no> wrote:
If we were to use git, we should have one git repository per package, and also provide one repository which includes all the packages as submodules.
Why not use one branch per package and one branch per repository with the packages as submodules instead of a repository for each package? This way all the packages would be in a single repository and could be fetched all at once or one at a time.
If you had one package on each branch, cloning the repository would bring down all of the packages together, because all of the branches in a git repository are fetched when you clone. Keeping unrelated code in different branches in the same repo is a bit weird in Git, and is not generally done; it almost always makes more sense to use a separate repo for each code base. Paul
From: pdgiddie@gmail.com To: arch-general@archlinux.org Date: Mon, 30 Sep 2013 10:32:26 +0100 Subject: Re: [arch-general] Git
On Monday 30 Sep 2013 05:13:57 Sebastian Schwarz wrote:
On 2013-29-09, Tom Gundersen <teg@jklm.no> wrote:
If we were to use git, we should have one git repository per package, and also provide one repository which includes all the packages as submodules.
Why not use one branch per package and one branch per repository with the packages as submodules instead of a repository for each package? This way all the packages would be in a single repository and could be fetched all at once or one at a time.
If you had one package on each branch, cloning the repository would bring down all of the packages together, because all of the branches in a git repository are fetched when you clone. Keeping unrelated code in different branches in the same repo is a bit weird in Git, and is not generally done; it almost always makes more sense to use a separate repo for each code base.
Paul
You don't have to pull down all the branches at the same time. Right now I maintain my own sub patch set for packages that I want stuffed added or removed to by useing git clone --single branch git clone --single-branch git://projects.archlinux.org/svntogit/packages.git -b packages/git then when I want another package from extra or core, i can fetch it git fetch origin packages/git git checkout -b packages/git FETCH_HEAD and you can git pull --rebase from origin in the same way Daniel
Hi On Mon, Sep 30, 2013 at 3:55 PM, Daniel Wallace <danielwallace@gtmanfred.com> wrote:
From: pdgiddie@gmail.com To: arch-general@archlinux.org Date: Mon, 30 Sep 2013 10:32:26 +0100 Subject: Re: [arch-general] Git
On Monday 30 Sep 2013 05:13:57 Sebastian Schwarz wrote:
On 2013-29-09, Tom Gundersen <teg@jklm.no> wrote:
If we were to use git, we should have one git repository per package, and also provide one repository which includes all the packages as submodules.
Why not use one branch per package and one branch per repository with the packages as submodules instead of a repository for each package? This way all the packages would be in a single repository and could be fetched all at once or one at a time.
If you had one package on each branch, cloning the repository would bring down all of the packages together, because all of the branches in a git repository are fetched when you clone. Keeping unrelated code in different branches in the same repo is a bit weird in Git, and is not generally done; it almost always makes more sense to use a separate repo for each code base.
Paul
You don't have to pull down all the branches at the same time.
Right now I maintain my own sub patch set for packages that I want stuffed added or removed to by useing git clone --single branch
git clone --single-branch git://projects.archlinux.org/svntogit/packages.git -b packages/git
then when I want another package from extra or core, i can fetch it
git fetch origin packages/git git checkout -b packages/git FETCH_HEAD
and you can git pull --rebase from origin in the same way
I think it makes more sense to use branches for stable/testing versions of the same sourcetree. Using branches to track different projects is indeed unusual way to use git.
participants (4)
-
Anatol Pomozov
-
Daniel Wallace
-
Paul Gideon Dann
-
Sebastian Schwarz