[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Pushing patches to staging
From: |
David Kastrup |
Subject: |
Re: Pushing patches to staging |
Date: |
Tue, 15 Nov 2011 17:46:43 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) |
"Phil Holmes" <address@hidden> writes:
> ----- Original Message -----
> From: "David Kastrup" <address@hidden>
> To: <address@hidden>
> Sent: Tuesday, November 15, 2011 2:43 PM
> Subject: Re: Pushing patches to staging
>
>
> Thanks, David. I've seen your earlier mail where you recommend:
>
> "Make sure that you fetch dev/staging. I find it easiest to fetch all:
> have something like the following in .git/config
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = ssh://git.sv.gnu.org/srv/git/lilypond.git"
>
> If I'm not doing much in the way of development, do you think it's
> worth fetching all the remote branches?
It's a rather cheap operation, actually, since git transfers only
"objects", so every file in such a branch that is the same as a file
somewhere in the already fetched history is not getting transferred.
> Is there a way just to fetch staging, and is this sensible?
I think you can have more than one fetch line, so you can just add
something like
fetch = +refs/heads/staging:refs/remotes/origin/staging
to the lines that are already there.
--
David Kastrup
- Re: Pushing patches to staging, (continued)
- Re: Pushing patches to staging, David Kastrup, 2011/11/12
- Re: Pushing patches to staging, Phil Holmes, 2011/11/13
- Re: Pushing patches to staging, David Kastrup, 2011/11/13
- Re: Pushing patches to staging, Carl Sorensen, 2011/11/13
- Re: Pushing patches to staging, Phil Holmes, 2011/11/15
- Re: Pushing patches to staging, David Kastrup, 2011/11/15
- Re: Pushing patches to staging, Phil Holmes, 2011/11/15
- Re: Pushing patches to staging,
David Kastrup <=
- Re: Pushing patches to staging, Phil Holmes, 2011/11/18
- Re: Pushing patches to staging, David Kastrup, 2011/11/18