All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: thomas@koch.ro, debian-devel@lists.debian.org,
	git@vger.kernel.org,  vcs-pkg-discuss@lists.alioth.debian.org
Subject: Re: elegant(?) debian topgit workflow?
Date: Thu, 24 Dec 2009 16:34:10 +0000	[thread overview]
Message-ID: <4B339802.7040003@dgreaves.com> (raw)
In-Reply-To: <94a0d4530912240714y798085d8r3bf88011e8ec782b@mail.gmail.com>

Felipe Contreras wrote:
> On Wed, Dec 16, 2009 at 12:13 PM, Thomas Koch <thomas@koch.ro> wrote:
>> branches
>> --------
>>
>> upstream
> 
> I would call it 'master'. That's how upstream would call it.
> 
>> debian/*, fixes/*, features/* - topgit branches based on upstream
>> patches - the hero
>> master - contains the debian/ dir and is the branch we build from
> 
> Think about other systems, like Ubuntu and Maemo, it would be nice to
> have branches both for Maemo and Debian on the same repo:
> debian - what you call 'master'
> debian-patches - what you call 'patches'
> maemo5 - contains the debian/ dir, but for Maemo 5
> maemo5-patches - patches for Maemo 5, might be based on top of debian-patches

I've been touting for feedback on this for a while :)

http://wiki.maemo.org/Mer/Build/UsingGitorious

David

-- 
"Don't worry, you'll be fine; I saw it work in a cartoon once..."

      reply	other threads:[~2009-12-24 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 10:13 elegant(?) debian topgit workflow? Thomas Koch
2009-12-24 15:14 ` Felipe Contreras
2009-12-24 16:34   ` David Greaves [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B339802.7040003@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=debian-devel@lists.debian.org \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=thomas@koch.ro \
    --cc=vcs-pkg-discuss@lists.alioth.debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.