Re: [Debian-med-packaging] Policy: git configuration
- To: debian-med@lists.debian.org
- Subject: Re: [Debian-med-packaging] Policy: git configuration
- From: Charles Plessy <plessy@debian.org>
- Date: Fri, 4 Jun 2010 10:58:20 +0900
- Message-id: <20100604015820.GC12726@kunpuu.plessy.org>
- In-reply-to: <AANLkTikUFsWvLsRq5UrUpaYZD1ZwdLIDSrSvQAoQpXh9@mail.gmail.com> <r2j7f45d9391005051037y3df52b60od9bc893227806edd@mail.gmail.com>
- References: <AANLkTikUFsWvLsRq5UrUpaYZD1ZwdLIDSrSvQAoQpXh9@mail.gmail.com> <r2j7f45d9391005051037y3df52b60od9bc893227806edd@mail.gmail.com>
Le Wed, May 05, 2010 at 10:37:29AM -0700, Shaun Jackman a écrit :
Le Sun, May 30, 2010 at 10:56:18AM -0700, Shaun Jackman a écrit :
> Hi,
>
> I'm a git newbie, and I stumbled around a bit before I found this git
> configuration gem:
> git config branch.master.remote origin
> git config branch.master.merge refs/heads/master
Hi Shaun,
sorry for not having answered you earlier. I was puzzled why I did not run in
the problem. I think that the reason is that after I make my initial push to
Alioth, I immediately replace the original repository by a clone from Alioth to
doublecheck if it is functional. And later I simply use debcheckout. In these
cases, the git configuration is automagic.
I will try to add a paragraph that summarises both approaches.
Have a nice day,
--
Charles
Reply to: