From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change to bzr build instructions
Date: Fri, 25 Mar 2011 12:18:04 +0200 [thread overview]
Message-ID: <83d3lftsf7.fsf@gnu.org> (raw)
In-Reply-To: <87aagj349j.fsf@fencepost.gnu.org>
> From: David Kastrup <dak@gnu.org>
> Date: Fri, 25 Mar 2011 11:04:24 +0100
>
> > Why were these files deleted and then created anew in autogen/? Why
> > not "bzr mv" them instead? Do we really want to lose their history?
>
> One thing that makes sense about git: moving files is exactly the same
> as deleting and recreating them.
Please stop the git propaganda here. The advantages and disadvantages
of git vs bzr in this regard are well known and can be found with
Google.
next prev parent reply other threads:[~2011-03-25 10:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 0:24 Change to bzr build instructions Glenn Morris
2011-03-21 0:46 ` Glenn Morris
2011-03-21 16:06 ` Jim Meyering
2011-03-21 22:33 ` Stefan Monnier
2011-03-22 3:31 ` Glenn Morris
2011-03-22 5:42 ` Stefan Monnier
2011-03-22 7:16 ` Glenn Morris
2011-03-22 8:08 ` Jim Meyering
2011-03-22 9:32 ` Andreas Schwab
2011-03-23 3:15 ` Glenn Morris
2011-03-22 11:36 ` Andreas Röhler
2011-03-22 13:09 ` Harald Hanche-Olsen
2011-03-22 18:37 ` Glenn Morris
2011-03-25 9:54 ` Eli Zaretskii
2011-03-25 10:04 ` David Kastrup
2011-03-25 10:18 ` Eli Zaretskii [this message]
2011-03-25 11:44 ` Leo
2011-03-25 13:07 ` David Kastrup
2011-03-25 13:13 ` Eli Zaretskii
2011-03-25 13:52 ` David Kastrup
2011-03-25 16:02 ` Eli Zaretskii
2011-03-25 13:45 ` Andreas Röhler
2011-03-27 18:54 ` Davis Herring
2011-03-25 14:37 ` Ted Zlatanov
2011-03-25 15:03 ` David Kastrup
2011-03-25 15:16 ` Ted Zlatanov
2011-03-25 15:32 ` David Kastrup
2011-03-25 16:08 ` Eli Zaretskii
2011-03-25 19:55 ` Stefan Monnier
2011-03-28 1:11 ` Miles Bader
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=83d3lftsf7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dak@gnu.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 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.