From: Juanma Barranquero <lekktu@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Please don't use revision numbers on commit messages (and elsewhere).
Date: Fri, 1 Apr 2011 12:34:33 +0200 [thread overview]
Message-ID: <AANLkTimG3G3oqLuXKedUwcwoduuSm_uLFmg1CGCsDT6=@mail.gmail.com> (raw)
In-Reply-To: <87k4fevkc1.fsf@wanadoo.es>
On Fri, Apr 1, 2011 at 03:20, Óscar Fuentes <ofv@wanadoo.es> wrote:
> Anyone can setup a public repo anytime, anywhere. Let's think of a
> long-lived feature branch of the type of lexbind or bidi which, for
> whatever reason, the participating developers finds more convenient to
> host outside of Savannah.
I think Eli has already answered that: if/when it happens, we can
discuss how to minimize the problems. Until now, it is entirely
hypothetical.
> In the case of patches, using revision ids on the commit messages is,
> actually, most convenient, because on that case the referenced ids are
> unambiguous no matter on which branch the patch is applied.
"Unambiguous" does not mean "I have it accessible and I know which
branch it refers to". Are you defending using revids because they are
unique, or because you don't like to having around multiple branches?
> On a distributed project, you don't know how many active branches exist
> out there.
Last time I checked, Emacs wasn't a "distributed project". It is a
centralized project with a distributed tool that helps developers.
> Let me expand with an example based on my past* experience. I have a
> number of heterogeneous machines (different OS, varying network
> connectivity, etc) and on all of them I have Emacs running (of
> course!). I've my private branch with some customizations, which is what
> I use for building and installing Emacs on all those machines. Keeping
> the private branch mirrored among all of them means work. Keeping
> mirrors for `trunk', emacs-23 and what-not is too much of a burden (last
> time I checked there was no simple & reliable method for synchronizing
> sets of branches across multiple platforms.)
Sorry, you lost me here. "trunk, emacs-23 and what-not" can be mostly
summarized to "trunk, emacs-23 and nothing else", *unless* you're
actively tracking window-pub, lexbind-new or some other branch, which
most people (even developers) apparently don't do. If we maintained
dozens of branches, all of them vibrant with activity, I could buy it.
But we use a development branch and a release branch, and a few
almost-private-development-branches-that-nobody-tracks, and that
doesn't seem likely to change in the near future.
> Do you prefer to wait until the problem has manifested itself on all its
> crudeness? :-)
Sure I do. And you know why? Because Bazaar revnos are *convenient*,
and Bazaar revids are a royal PITA. I don't want to abandon convenient
shorthands for what, at the moment, is just FUD.
Juanma
next prev parent reply other threads:[~2011-04-01 10:34 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 20:47 Please don't use revision numbers on commit messages (and elsewhere) Óscar Fuentes
2011-03-31 21:36 ` Lennart Borgman
2011-03-31 21:53 ` Óscar Fuentes
2011-03-31 21:59 ` Lennart Borgman
2011-03-31 22:06 ` Óscar Fuentes
2011-03-31 22:18 ` Lennart Borgman
2011-03-31 22:58 ` Juanma Barranquero
2011-04-01 7:42 ` Eli Zaretskii
2011-04-01 7:58 ` Andreas Schwab
2011-04-01 8:02 ` Eli Zaretskii
2011-04-01 8:17 ` Andreas Schwab
2011-04-01 8:42 ` Eli Zaretskii
2011-04-01 8:54 ` Andreas Schwab
2011-04-01 10:11 ` Eli Zaretskii
2011-04-01 10:21 ` Andreas Schwab
2011-04-01 10:48 ` Eli Zaretskii
2011-04-01 11:18 ` Andreas Schwab
2011-04-01 13:15 ` Eli Zaretskii
2011-04-01 13:32 ` Andreas Schwab
2011-04-01 13:47 ` Eli Zaretskii
2011-04-01 13:51 ` Deniz Dogan
2011-04-01 15:26 ` Óscar Fuentes
2011-04-01 19:13 ` Eli Zaretskii
2011-04-01 20:17 ` Óscar Fuentes
2011-03-31 23:14 ` Juanma Barranquero
2011-04-01 0:11 ` Óscar Fuentes
2011-04-01 0:28 ` Juanma Barranquero
2011-04-01 1:20 ` Óscar Fuentes
2011-04-01 8:18 ` Eli Zaretskii
2011-04-01 12:08 ` David Kastrup
2011-04-01 13:15 ` Eli Zaretskii
2011-04-01 15:35 ` Óscar Fuentes
2011-04-01 19:52 ` Eli Zaretskii
2011-04-01 20:04 ` David Kastrup
2011-04-01 20:36 ` Eli Zaretskii
2011-04-01 20:43 ` Óscar Fuentes
2011-04-01 10:34 ` Juanma Barranquero [this message]
2011-04-01 15:55 ` Óscar Fuentes
2011-04-01 21:53 ` Juanma Barranquero
2011-04-04 16:32 ` Nils Ackermann
2011-04-04 21:27 ` Juanma Barranquero
2011-04-04 21:36 ` Lennart Borgman
2011-04-04 21:49 ` Juanma Barranquero
2011-04-04 22:03 ` Lennart Borgman
2011-04-04 22:09 ` Juanma Barranquero
2011-04-04 22:27 ` Stefan Monnier
2011-04-04 22:35 ` Juanma Barranquero
2011-04-05 21:00 ` Thien-Thi Nguyen
2011-04-05 21:00 ` Thien-Thi Nguyen
2011-04-06 1:30 ` Stefan Monnier
2011-04-06 2:55 ` Stephen J. Turnbull
2011-04-06 12:47 ` Thien-Thi Nguyen
2011-04-01 1:59 ` Stephen J. Turnbull
2011-04-01 10:00 ` Uday S Reddy
2011-04-01 15:00 ` Stephen J. Turnbull
2011-04-01 16:38 ` Uday S Reddy
2011-04-01 18:08 ` Stephen J. Turnbull
2011-04-01 18:56 ` Uday S Reddy
2011-04-01 20:49 ` Stephen J. Turnbull
2011-04-01 10:45 ` Juanma Barranquero
2011-04-01 14:51 ` Stefan Monnier
2011-04-01 15:14 ` Ted Zlatanov
2011-04-01 19:58 ` Juanma Barranquero
2011-04-02 2:12 ` Chong Yidong
2011-04-01 1:35 ` Stephen J. Turnbull
2011-04-01 10:39 ` Juanma Barranquero
2011-03-31 23:16 ` Thien-Thi Nguyen
2011-04-01 0:20 ` Óscar Fuentes
2011-04-01 8:38 ` Thien-Thi Nguyen
2011-04-01 9:36 ` Eli Zaretskii
2011-04-01 10:14 ` Eli Zaretskii
2011-04-01 17:38 ` Thien-Thi Nguyen
2011-04-01 15:38 ` Óscar Fuentes
2011-04-01 19:12 ` Eli Zaretskii
2011-04-01 20:21 ` Óscar Fuentes
2011-04-01 20:38 ` Eli Zaretskii
2011-04-01 21:40 ` Uday S Reddy
2011-04-02 0:03 ` Óscar Fuentes
2011-04-02 6:20 ` Uday S Reddy
2011-04-02 13:47 ` Óscar Fuentes
2011-04-03 8:00 ` Uday S Reddy
2011-04-03 16:13 ` Óscar Fuentes
2011-04-04 9:29 ` Uday S Reddy
2011-04-05 2:20 ` Stephen J. Turnbull
2011-04-02 2:57 ` Stephen J. Turnbull
2011-04-01 0:55 ` Stefan Monnier
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='AANLkTimG3G3oqLuXKedUwcwoduuSm_uLFmg1CGCsDT6=@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).