From: Catalin Marinas <catalin.marinas@gmail.com>
To: Marco Costalba <mcostalba@yahoo.it>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Patches exchange is bad?
Date: Thu, 18 Aug 2005 14:41:06 +0100 [thread overview]
Message-ID: <tnx7jej2wi5.fsf@arm.com> (raw)
In-Reply-To: <20050818133411.15529.qmail@web26306.mail.ukl.yahoo.com> (Marco Costalba's message of "Thu, 18 Aug 2005 06:34:10 -0700 (PDT)")
Marco Costalba <mcostalba@yahoo.it> wrote:
> I was thinking at two different kind of workflow, one were you are
> tracking a remote repository ( Linux kernel project like ) and one
> as single developer with both stable and develop lines ( qgit or
> StGIT ;-) projects like ).
There is another option for the 2nd case, where you maintain both both
stable and development. You could use 'git push' to the stable
repository (actually, more like a mirror) and make the
StGIT-maintained repository track the changes from the stable one and
just update it with 'stg pull'
--
Catalin
next prev parent reply other threads:[~2005-08-18 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 13:34 [RFC] Patches exchange is bad? Marco Costalba
2005-08-18 13:41 ` Catalin Marinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 10:00 Marco Costalba
2005-08-18 11:16 ` Catalin Marinas
2005-08-17 18:03 Marco Costalba
2005-08-17 17:35 Marco Costalba
2005-08-17 21:27 ` Catalin Marinas
2005-08-17 21:37 ` Johannes Schindelin
2005-08-18 10:27 ` Catalin Marinas
2005-08-17 8:27 Marco Costalba
2005-08-17 9:07 ` Martin Langhoff
2005-08-16 22:09 Marco Costalba
2005-08-16 22:45 ` Daniel Barkalow
2005-08-16 21:47 Marco Costalba
2005-08-16 20:01 Marco Costalba
2005-08-16 20:39 ` Johannes Schindelin
2005-08-16 21:02 ` Junio C Hamano
2005-08-16 21:31 ` Martin Langhoff
2005-08-17 17:12 ` Catalin Marinas
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=tnx7jej2wi5.fsf@arm.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).