all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: grischka <grishka@gmx.de>
To: lennart.borgman@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Making the tarball with bzr data (was: bzr repository ready?)
Date: Mon, 30 Nov 2009 19:11:27 +0100	[thread overview]
Message-ID: <4B140ACF.9090808@gmx.de> (raw)

> If I already have all the Emacs files locally (possibly with some
> changes) how do I do to make this a bazaar thing? (This must be the
> most common situation, or?)

In any case you need to get the official emacs bazaar repository
first.

If you have personal changes, create a branch.

Then, either:
1) copy your changed files over the ones in that branch
2) commit the resulting change as one single patch.

Or, if you have more than one change and want to have separate
commits for each, use a merge tool such as WinMerge:
1) compare your directory tree with the new development branch
2) For each feature:
    - copy the relevant chunks that affect the feature
    - commit with some message
    - repeat 2) until no differences are left.

Then you could publish your branch for others to test or improve.

HTH, grischka





             reply	other threads:[~2009-11-30 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 18:11 grischka [this message]
2009-11-30 18:15 ` Making the tarball with bzr data (was: bzr repository ready?) Lennart Borgman
2009-11-30 19:35   ` Making the tarball with bzr data Óscar Fuentes
2009-11-30 21:27     ` Lennart Borgman
2009-11-30 21:50       ` Stefan Monnier
2009-11-30 22:33         ` Lennart Borgman
2009-12-01  3:24           ` Stefan Monnier
2009-11-30 22:44       ` Óscar Fuentes
2009-12-01  2:20       ` Stephen J. Turnbull
2009-12-01  2:40         ` Óscar Fuentes
2009-12-04 18:47       ` Giorgos Keramidas
  -- strict thread matches above, loose matches on Subject: below --
2009-10-30 23:38 bzr repository ready? Andreas Schwab
2009-11-09 16:53 ` Karl Fogel
2009-11-09 23:56   ` Andreas Schwab
2009-11-11 22:45     ` Karl Fogel
2009-11-12 13:55       ` Andreas Schwab
2009-11-12 18:31         ` Karl Fogel
2009-11-12 20:18           ` Stefan Monnier
2009-11-12 20:57             ` Karl Fogel
2009-11-13  9:42               ` Andreas Schwab
2009-11-18 22:29                 ` Karl Fogel
2009-11-18 23:09                   ` Alan Mackenzie
2009-11-19  5:31                     ` Karl Fogel
2009-11-20 13:34                       ` Eli Zaretskii
2009-11-20 19:22                         ` Karl Fogel
2009-11-21 19:01                           ` Glenn Morris
2009-11-22 23:41                             ` Karl Fogel
2009-11-23  4:36                               ` Eli Zaretskii
2009-11-23  5:11                                 ` Óscar Fuentes
2009-11-23  5:50                                   ` Stefan Monnier
2009-11-23  7:35                                     ` Stephen J. Turnbull
2009-11-23 14:39                                       ` Stefan Monnier
2009-11-24  2:56                                         ` Making the tarball with bzr data (was: bzr repository ready?) Óscar Fuentes
2009-11-30 16:34                                           ` Lennart Borgman

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=4B140ACF.9090808@gmx.de \
    --to=grishka@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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.