Hi Bas,

On Tue, Sep 02, 2014 at 07:47:37AM +0200, Sebastiaan Couwenberg wrote:
> On 09/01/2014 11:44 PM, Andreas Tille wrote:
> > On Mon, Sep 01, 2014 at 11:40:40PM +0200, Sebastiaan Couwenberg wrote:
> >>
> >> Make sure the origin is up to date, and checkout the branch:
> >>
> >>  git fetch origin
> >>  git checkout wheezy
> > 
> > $ git fetch origin
> > $ git branch
> > * master
> >   pristine-tar
> >   upstream
> > $ git checkout wheezy
> > Branch wheezy konfiguriert zum Folgen von Remote-Branch wheezy von origin.
> > Gewechselt zu einem neuem Branch 'wheezy'
> > 
> > Am I doing something wrong?

I think I might not have done anything wrong since when I'm looking
today into the repository I was in branch wheezy.  It seems that `git
branch` is showing this only after I checked it out.   I'd call this a
> The qlandkartegt repo should also have a up/doc branch, I have it
> checked out via `gbp-clone --all`, do you have it in your remote?

When doing a `git branch` (while beeing in wheezy branch) I dit not see
up/doc branch ... only after `git checkout up/doc`.  That's *very*
confusing behaviour to my perception.  I assumed `git branch` gives a
list of all possible branches to enable me to pick one to check it out.
I did not assumed that I need to wild guess what branches might exist to
be able to check it out and only afterwards get a list of those branches
I visited.  That's adventure games style. :-(
>  git branch -av

I should learn to use these options by default...

>  git remote -v
> I just did a fresh clone of the repo, and I get the wheezy branch just fine:
>  git clone git://anonscm.debian.org/pkg-grass/qlandkartegt.git
>  cd qlandkartegt/
>  git checkout pristine-tar
>  git checkout upstream
>  git checkout wheezy
> I'm not sure what's going on at your end, maybe the remote still points
> to collab-maint where the repo no longer exists?

No, I never cloned from collab-maint.

Kind regards



Pkg-grass-devel mailing list

Reply via email to