Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: The Gnus repository is switching to Git as of 2010-04-19
Date: Tue, 20 Apr 2010 18:44:34 -0500	[thread overview]
Message-ID: <878w8hofj1.fsf@lifelogs.com> (raw)
In-Reply-To: <jwvhbn5rcix.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 20 Apr 2010 18:28:45 -0400")

On Tue, 20 Apr 2010 18:28:45 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>> Git doesn't really do renames, but "git diff" will detect them if the
>> deleted and the new file have the same content.

SM> I know that's how it works.  But I don't know what it means in terms of
SM> the behavior when merging changes, including addition/removal of files.
SM> IIUC it understands movement of files, but does it understand movement
SM> of directories (e.g. if Gnus adds a new file lisp/gnus-new.el, will it
SM> appear in Emacs as lisp/gnus/gnus-new.el or lisp/gnu-new.el?; similarly
SM> if Emacs adds a new file lisp/new.el will it appear in Gnus as
SM> lisp/new.el?).

Sorry, I'm learning some dark corners of Git so I don't assume everyone
knows how Git tracks blobs and indexes them.  It's supposed to find the
files by content across the tree, so a renamed file from either side
*should* be tracked correctly.  I'll have to try it to be sure.

Assuming this rename tracking works well, new files will be managed by
the Gnus synchronization maintainer.  The Emacs side should be
authoritative for new files, meaning that we (Gnus) will get lisp/new.el
and have to remove it, and that we will push our lisp/gnus-new.el to
your lisp/gnus/gnus-new.el.

SM> I don't personally care whether the moves&removal&adds are done on the
SM> Bzr or Git side.  AFAIK it's as easy to do it on either side.  It can
SM> even be split into some part on one side and some other part on the
SM> other side.

Let's keep all the work on the Git side.  I haven't heard anyone else
recommend a better workflow than "all on the Git side" yet.  So,
assuming the above, you or Yidong will not do anything special.  You
just need to tell us which Emacs branches should be synchronized with
the corresponding Gnus branches (let's keep the number down so it
doesn't become too much work).  I assume Emacs trunk will synchronize
with Gnus trunk; what other branches do we need immediately?

On the Gnus side I will experiment and try to develop a scripted
procedure, but it should be readily usable by anyone.

Thanks for your help
Ted




  reply	other threads:[~2010-04-20 23:44 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 17:34 Ted Zlatanov
2010-04-19 18:21 ` Sivaram Neelakantan
2010-04-19 19:13   ` Ted Zlatanov
2010-04-21  8:50     ` Steinar Bang
2010-04-21  9:01       ` David Engster
2010-04-21  9:02         ` David Engster
2010-04-21 10:05       ` Andreas Schwab
2010-04-21 12:12         ` Andreas Schwab
2010-04-21 14:10           ` Ted Zlatanov
2010-04-21 14:54             ` Andreas Schwab
2010-04-23  0:55               ` Ted Zlatanov
2010-04-22  8:12           ` Steinar Bang
2010-04-19 19:17   ` Sven Joachim
2010-04-20 13:03 ` Harry Putnam
2010-04-20 13:29   ` Ted Zlatanov
2010-04-20 13:57   ` Andreas Schwab
     [not found] ` <jwvr5mb8evr.fsf-monnier+emacs@gnu.org>
2010-04-20 13:55   ` Ted Zlatanov
2010-04-20 15:00     ` Stefan Monnier
2010-04-20 20:05       ` Ted Zlatanov
2010-04-20 22:28         ` Stefan Monnier
2010-04-20 23:44           ` Ted Zlatanov [this message]
2010-04-21  3:16             ` Stefan Monnier
2010-04-21 11:03               ` Gnus Git synchronization with Emacs Bazaar (was: The Gnus repository is switching to Git as of 2010-04-19) Ted Zlatanov
2010-04-22  2:24                 ` Stephen J. Turnbull
2010-04-21  0:33           ` The Gnus repository is switching to Git as of 2010-04-19 Stephen J. Turnbull
2010-04-21  0:51             ` Ted Zlatanov
2010-04-21  3:31               ` Stephen J. Turnbull
2010-04-21  3:11             ` Stefan Monnier
2010-04-21  4:00               ` Stephen J. Turnbull
2010-04-21  9:01           ` Andreas Schwab
2010-04-21  2:59         ` Teemu Likonen
2010-04-21 11:30           ` Ævar Arnfjörð Bjarmason
2010-04-21 14:57             ` Teemu Likonen
2010-04-21 16:36               ` Ævar Arnfjörð Bjarmason
2010-04-23  1:09         ` cgit beautification (was: The Gnus repository is switching to Git as of 2010-04-19) Ted Zlatanov
2011-02-25 22:04           ` cgit beautification Ted Zlatanov
2011-02-25 22:56             ` Adam Sjøgren
2011-02-25 23:19             ` Adam Sjøgren
2011-02-26 12:05               ` Lars Ingebrigtsen
2011-03-01 10:27               ` Ted Zlatanov
2011-03-01 10:30                 ` Ted Zlatanov
2011-03-01 11:31                   ` Adam Sjøgren
2011-03-01 13:32                     ` Ted Zlatanov
2011-03-01 17:08                       ` Adam Sjøgren
2011-03-02 11:05                         ` Ted Zlatanov
2010-04-22  5:49     ` The Gnus repository is switching to Git as of 2010-04-19 Harry Putnam
2010-04-23  0:36       ` Ted Zlatanov

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=878w8hofj1.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).