From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Strange message from "bzr pull"
Date: Wed, 30 Dec 2009 06:16:28 +0200 [thread overview]
Message-ID: <837hs5drkz.fsf@gnu.org> (raw)
In-Reply-To: <871vidnyon.fsf@telefonica.net>
> From: Óscar_Fuentes <ofv@wanadoo.es>
> Date: Wed, 30 Dec 2009 00:32:56 +0100
>
> Distributed version control is about exchanging revisions. You need a
> way to know what revisions you are missing from some other branch, and a
> way to know how the revisions are arranged. Those unique revision-ids
> are the solution.
But that makes sense only for branches bounded to remote repositories,
right? For my own local branches, there's nothing interesting in this
information.
> > revno: 99212 [merge]
> > revision-id: nickrob@snap.net.nz-20091229072200-2capgobhol086ef3
> > parent: dann@ics.uci.edu-20091229064608-lpeenthwsy3zp0vy
> > parent: nickrob@snap.net.nz-20091229071534-bdspozxb6idtp7z0
>
> This revision has two parents because it is a merge point. I'm sure you
> get the idea.
Yes, it looked so utterly trivial that I wondered why you were saying
it was ``key information that made DVCS possible''.
next prev parent reply other threads:[~2009-12-30 4:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 7:43 Strange message from "bzr pull" Eli Zaretskii
2009-12-29 10:18 ` Juanma Barranquero
2009-12-29 10:30 ` Eli Zaretskii
2009-12-29 12:40 ` Juanma Barranquero
2009-12-29 16:24 ` Eli Zaretskii
2009-12-29 17:00 ` Karl Fogel
2009-12-29 18:10 ` Eli Zaretskii
2009-12-29 18:13 ` Juanma Barranquero
2009-12-29 18:34 ` Eli Zaretskii
2009-12-29 19:28 ` Óscar Fuentes
2009-12-29 19:51 ` Karl Fogel
2009-12-29 20:04 ` Óscar Fuentes
2009-12-29 20:15 ` Karl Fogel
2009-12-29 20:29 ` Eli Zaretskii
2009-12-29 23:32 ` Óscar Fuentes
2009-12-30 4:16 ` Eli Zaretskii [this message]
2009-12-30 5:15 ` Óscar Fuentes
2009-12-31 9:39 ` Stephen J. Turnbull
2009-12-29 20:16 ` Eli Zaretskii
2009-12-29 23:14 ` Óscar Fuentes
2009-12-30 4:21 ` Eli Zaretskii
2009-12-30 4:28 ` Miles Bader
2009-12-30 5:26 ` Óscar Fuentes
2009-12-29 18:44 ` Karl Fogel
2009-12-29 19:01 ` Eli Zaretskii
2009-12-29 19:09 ` Karl Fogel
2009-12-29 20:09 ` Eli Zaretskii
2009-12-30 7:02 ` Eli Zaretskii
2009-12-30 12:19 ` Juanma Barranquero
2009-12-30 15:05 ` Eli Zaretskii
2009-12-30 15:19 ` Juanma Barranquero
2009-12-31 19:36 ` Karl Fogel
2009-12-31 20:49 ` Juanma Barranquero
2009-12-29 21:37 ` Stefan Monnier
2009-12-31 9:43 ` Stephen J. Turnbull
2009-12-29 18:02 ` Eli Zaretskii
2009-12-29 18:12 ` Juanma Barranquero
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=837hs5drkz.fsf@gnu.org \
--to=eliz@gnu.org \
--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).