Re: repository moved to gitlab.com

Hi,

>> If the resulting directory is indeed where I should now be building
>Yes, you can build in a git checkout (or a subdirectory thereof).

Depending on the number of changes you plan to do an alternative which I've used a lot is as follows:

- Have one directory were only clisp's git resides -- you don't even need to extract the source there. You only pull/fetch from the gitlab master server. This is your local copy of clisp' git repository.

- Have another directory which is a shallow/bare clone of your repository.
This is where you check out and possibly do modifications.
$ git-clone --local --shared -n ~/src/git/clisp/.git clisp-work

Advantage:
- The local repositories are tiny (from a git POV) and contain only your local changes.
  After all changes there have been sent & accepted upstream, simply rm -rf one.
- The larger clisp mirror only fetches updates from upstream, so there's never any conflict there, ever.

Drawback:
- Need to *both* git-fetch or git-pull the work repository from the local src repository and the src from gitlab, from time to time
(and corresponding git reset --hard when using git-fetch, to advance the HEAD).

Yet if all you want to do is "fetch/pull && compile || report" this dual setup is overkill.
Unless you have a compile farm, that is; or you plan to work on several branches at the same time, e.g. socket-trouble, postgresql-update, macosx-tree.

Another thing which I've used is (beware, my notes are old):
; Imitate git clone but track only selected branches:
$ mkdir project.git
$ cd project.git
$ git init
$ git remote add -f -t master -m master origin git://example.com/git.git/

Regards,
	Jörg

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel