From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Using Git to manage your Emacs changes
Date: Fri, 09 Apr 2010 08:04:16 +0200 [thread overview]
Message-ID: <87bpdtnov3.fsf@tux.homenetwork> (raw)
In-Reply-To: 176F7809-3090-4664-BFFF-84F25DDD9F10@gmail.com
John Wiegley <jwiegley@gmail.com> writes:
> On Apr 7, 2010, at 4:37 PM, Thierry Volpiatto wrote:
>
>> Why not using a stack of patchs like stgit or mercurial qpatchs.
>> You can then apply these patchs to bzr repo.
>
> I don't see how stgit improves anything. Also, I'm using git-bzr
> because I need to fetch the mirrored commits back into Git immediately
> after pushing, and I'm not sure how often the GitHub emacs mirror
> updates itself.
I use http://repo.or.cz/w/emacs.git
This repo is converted to a hg repo locally.
I have cloned this hg repo to another hg repo that handle qpatchs.
So i have three repos:
git, hg, hg qpatch.
1) on git repo: git pull
2) on hg repo: hg convert <last git revision>
(when the repo exists, hg convert is as fast as a pull)
3) on hg qpatch repo: hg pull
4) make some new patchs on hg qpatch repo (i use DVC and
anything-mercurial.el)
5) Then you can send patchs to Emacs or apply these patchs to bzr repo
directly.(your patchs have to be in git format)
The same can be done with stg.(with only 2 repo)
--
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/
next prev parent reply other threads:[~2010-04-09 6:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 19:23 Using Git to manage your Emacs changes John Wiegley
2010-04-07 19:32 ` David Reitter
2010-04-07 20:25 ` John Wiegley
2010-04-07 21:22 ` David Reitter
2010-04-21 17:30 ` Ted Zlatanov
2010-04-21 18:12 ` David Reitter
2010-04-21 19:29 ` John Wiegley
2010-04-21 20:42 ` Eli Zaretskii
2010-04-22 7:17 ` John Wiegley
2010-04-22 9:41 ` Lennart Borgman
2010-04-22 10:28 ` Andreas Schwab
2010-04-22 11:09 ` Lennart Borgman
2010-04-22 11:29 ` Andreas Schwab
2010-04-22 16:20 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Glenn Morris
2010-04-22 17:02 ` endless version control debates Óscar Fuentes
2010-04-22 17:07 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 17:52 ` Chad Brown
2010-04-22 19:16 ` Andreas Schwab
2010-04-22 20:09 ` Chad Brown
2010-04-23 2:50 ` endless version control debates Miles Bader
2010-04-22 20:16 ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 20:46 ` Eli Zaretskii
2010-04-22 21:10 ` Jeff Clough
2010-04-22 10:40 ` Using Git to manage your Emacs changes Miles Bader
2010-04-23 8:38 ` Juri Linkov
2010-04-23 9:29 ` Ævar Arnfjörð Bjarmason
2010-04-24 13:20 ` Richard Stallman
2010-04-24 15:27 ` Jason Earl
2010-04-24 15:45 ` Ævar Arnfjörð Bjarmason
2010-04-24 17:10 ` Alfred M. Szmidt
2010-04-24 19:33 ` Jason Earl
2010-04-24 20:33 ` Alfred M. Szmidt
2010-04-24 20:36 ` Eli Zaretskii
2010-04-24 21:54 ` Jason Earl
2010-04-25 8:26 ` Stephen J. Turnbull
2010-04-27 20:59 ` Karl Fogel
2010-04-25 16:47 ` Georg Brandl
2010-04-26 14:33 ` Richard Stallman
2010-04-26 17:35 ` Eli Zaretskii
2010-04-21 22:16 ` Andreas Schwab
2010-04-07 20:53 ` Giuseppe Scrivano
2010-04-07 20:37 ` Thierry Volpiatto
2010-04-08 22:27 ` John Wiegley
2010-04-08 22:43 ` Jonas Bernoulli
2010-04-09 6:04 ` Thierry Volpiatto [this message]
2010-04-08 16:57 ` Ken Raeburn
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=87bpdtnov3.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.