unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Glenn Morris <rgm@gnu.org>,
	Emacs developers <emacs-devel@gnu.org>,
	Juanma Barranquero <lektu@terra.es>, Miles Bader <miles@gnu.org>
Subject: Re: org changes lost
Date: Tue, 25 Nov 2008 10:38:49 +0100	[thread overview]
Message-ID: <118325E6-ED11-4519-BF12-8086BEA715A1@gmail.com> (raw)
In-Reply-To: <jwvmyfo7cm5.fsf-monnier+emacs@gnu.org>


On Nov 25, 2008, at 3:50 AM, Stefan Monnier wrote:

>> My skills in version control my not be sufficient to do this, jumping
>> between different version control worlds.
>
> You just need to reflect the branch of one into a branch of the other
> (one-way only), so it's not that difficult.  E.g. you can commit (via
> naive overwrite&commit) your externally-maintaned code into a special
> branch in the CVS, and then use cvs to merge the changes from that
> branch into the trunk.
>
> Or you can do it the other way around and take a copy of Emacs's trunk
> every once in a while, commit it onto a special branch in your main
> VCS (e.g. Bzr or Git), and then merge that branch into your main  
> branch.
>
> The safer thing to do (when working between VCS or without VCS) is to
> never copy files, but only ever take diffs and apply them.  It's not
> like taking diffs is safer but it forces you to think "diff between  
> what
> and what", so it makes it more likely that you'll do the right thing.

Yes, this sounds like the sane thing todo.  However, there are  
complications for this, such as the fact that the directory structure  
in my own repo is slightly different, and that I need to change the  
commit dates in the ChangeLog file when updating the files in Emacs,  
so at least for me tere is always some hand fiddling involved.

>
>
>> So I work by applying changed in Emacs to my local copy and reserve  
>> the
>> right to undo changes made in Emacs (not that this has been necessary
>> recently).  Usually this works OK, occasionally, like yesterday,
>> I miss something.
>
> To avoid this, try to do a "diff since last sync" and apply that to
> Emacs's repository.  This may result in conflicts, but only if there  
> are
> concurrent changes that you need to pay attention to.

Yes.  I do follow Emacs development through a git mirror, and since
yesterday I do have a local tag that is called last-sync-with-org-repo.
At lease as a double-checking mechanism this will be effective, I hope.

Thanks

- Carsten




  parent reply	other threads:[~2008-11-25  9:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 23:53 org changes lost Glenn Morris
2008-11-24  2:36 ` Glenn Morris
2008-11-24  3:56   ` Miles Bader
2008-11-24 12:31     ` Carsten Dominik
2008-11-24 16:32       ` Chong Yidong
2008-11-25  9:30         ` Carsten Dominik
2008-11-24 17:29       ` Glenn Morris
2008-11-24 19:31         ` Bastien
2008-11-24 18:23       ` Reiner Steib
2008-11-25  9:24         ` Bastien
2008-11-25 17:44           ` Reiner Steib
2008-11-25  9:31         ` Carsten Dominik
2008-11-25  2:50       ` Stefan Monnier
2008-11-25  3:10         ` Chong Yidong
2008-11-25 15:11           ` Stefan Monnier
2008-11-25  9:01         ` Yavor Doganov
2008-11-25 15:14           ` Stefan Monnier
2008-11-25  9:03         ` Bastien
2008-11-25  9:33           ` Carsten Dominik
2008-11-25 15:19           ` Stefan Monnier
2008-11-25 17:11             ` Bastien
2008-11-25  9:38         ` Carsten Dominik [this message]
2008-11-26  3:20           ` Michael Olson
2008-11-24 11:06 ` Carsten Dominik

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=118325E6-ED11-4519-BF12-8086BEA715A1@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@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).