Re: Problems cloning a git repository
On Sat, Jul 11, 2009 at 07:28:11PM +0200, Loïc Martin wrote:
> > git clone git+ssh://<username>@git.debian.org/git/pkg-games/<package>.git
> works, but it only pulls master (there should also be prisine-tar and
> upstream), and without pulling previous commits in the log for master.
Try git branch -lr
You should see all your remote branches if they are indeed in the repo.
> The second step plain doesn't work
>> git-pull origin +refs/remotes/*:refs/remotes/*
> First, it seem it should be git pull and not git-pull, but I can't
> verify that, only that there's a pull option for git while I can't find
> the git-pull command in any package.
Yes, git-hyphen-command was deprecated.
> I don't have any branches however (.git/branches has always been empty
> for my package) so I don't know how to solve that.
That's not important. You always have at least one branch (such as master).
>> git-import-orig [--pristine-tar] [-u version] /path/to/upstream-version.tar.gz
>
> Does this also commit the changes to Altioth, or do I have to do a git
> commit -a afterwards? The wiki seem to imply it's not necessary, and I
> don't remember having any trouble previously, but when I try to import a
> new upstream tarball in my badly cloned git repository, it doesn't and
> I'd probably have to use git commit -a (except the wiki doesn't say so,
> and I'd rather make sure before messing up the repository on Alioth).
That script will commit the upstream changes to your local repository.
It will not send your branches to Alioth unless you then do a git push.
Reply to: