From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: bzr help, please
Date: Fri, 01 Jul 2011 01:25:44 +0200 [thread overview]
Message-ID: <m3oc1ej407.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 4E0D0407.7000205@cs.ucla.edu
Paul Eggert <eggert@cs.ucla.edu> writes:
> I am leaving out all the intermediate steps where I get real work done
> (e.g., resolving merge conflicts), but I hope you get the idea.
Yeah. But I'm wondering whether it's easier to just go back to the
bound branch thingie. :-) I usually do rather small things on the
Emacs code, so the main annoyance is that it takes so long to check
stuff in.
But I think it's perhaps easier to solve that by having a separate Emacs
that I only use for vc mode.
Currently my work flow is
* change some stuff in some functions
* test it
* "bzr update"
* write the changelog really really fast so that there's no other
commits getting in my way
* commit from vc-mode
The "write the ChangeLogs reall really fast" is, perhaps, the most
annoying bit. Because if I get a ChangeLog conflict, that's five
minutes out the window while conflict-resoluting, bzr updating again,
checking in again...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-06-30 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 22:26 bzr help, please Lars Magne Ingebrigtsen
2011-06-30 23:17 ` Paul Eggert
2011-06-30 23:25 ` Lars Magne Ingebrigtsen [this message]
2011-07-01 7:06 ` Eli Zaretskii
2011-07-01 10:14 ` Lars Magne Ingebrigtsen
2011-07-01 11:05 ` Eli Zaretskii
2011-07-01 11:08 ` Lars Magne Ingebrigtsen
2011-07-01 14:26 ` Stefan Monnier
2011-07-01 14:51 ` Lars Magne Ingebrigtsen
2011-07-04 13:57 ` Lars Magne Ingebrigtsen
2011-07-04 17:26 ` Stefan Monnier
2011-07-05 15:20 ` Lars Magne Ingebrigtsen
2011-07-04 17:29 ` Stefan Monnier
2011-07-01 11:48 ` Juanma Barranquero
2011-07-01 14:07 ` Eli Zaretskii
2011-07-01 14:32 ` Juanma Barranquero
2011-06-30 23:18 ` Andreas Schwab
2011-07-01 3:03 ` Stefan Monnier
2011-07-01 6:58 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oc1ej407.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).