On 16/05/10 22:30, sc wrote:
On Sunday 16 May 2010 2:19:53 pm Tony Mechelynck wrote:

meaning it is supported but currently not set. My post was not
  about  Vim's 'relativenumber' option not being supported but
  about no "Included patches" in the :version output. Do you
  have that "Included patches" line? I don't, so the next time
  I report a 7.3a bug it won't be easy for me to say precisely
  which patches were or weren't included compared to the first
  7.3a set of sources issued by Bram. And, as I said, saying
  that I am "at relative changeset #2193" won't mean a thing,
  because every commit that I do (e.g. after a merge, including
  those done implicitly by fetch) adds an ordinal number not
  present in Bram's repo. Every merge that you commit also adds
  one, but I bet we don't do them exactly as frequently, so one
  of us will have more changesets than the other in his local
  repo, even if we have the exact same set of official patches
  included.

forgive me, please, for misunderstanding you, and probably also
for snipping in mid-sentence

my question now is, what would you have bram do?  7.3 is beta --
he is patching 7.2 -- would you like him to create two sets of
patches, each with different names but with the same content?

7.2.434    ==    7.3.001
7.2.435    ==    7.3.002
7.2.436    ==    7.3.003

i believe he does quite enough as it is, and i do not go looking
for ways to make it more complicated for him

sc


Bram will do what he will do. Since 7.3 (final) isn't released yet, he might (if he thinks it worth while) make patches labeled 7.3a.001, 7.3a.002, etc., which may or may not reflect 7.2 patches above 433. (I imagine it is quite possible that some 7.3a patches won't be ported back to 7.2.) I think (but maybe he thinks otherwise) that if he does it will be easier for everyone including him when someone finds a bug, so that one may say e.g. "I get this crash in gvim 7.3a.008 with GTK2 GUI" and everyone will understand, and maybe some other regular will pass by and say "Oh, but that was fixed in 7.3a.012". Or else, if someone proposes a patch, "This patch is against 7.3a.007 sources" and again the meaning will be obvious, even though with context diffs (well, unified diffs now, since hg diff never produces "classical" context diffs) patch can usually figure how many lines up or down to apply the patch, and with the "diff -r af32cb245cca src/misc.c" (or similar) line at the top, Mercurial might know how to merge even though it's not very "human-readable".


Best regards,
Tony.
--
RULES OF EATING -- THE BRONX DIETER'S CREED
        (1)  Never eat on an empty stomach.
        (2)  Never leave the table hungry.
        (3)  When traveling, never leave a country hungry.
        (4)  Enjoy your food.
        (5)  Enjoy your companion's food.
        (6)  Really taste your food.  It may take several portions to
             accomplish this, especially if subtly seasoned.
        (7)  Really feel your food.  Texture is important.  Compare,
             for example, the texture of a turnip to that of a
             brownie.  Which feels better against your cheeks?
        (8)  Never eat between snacks, unless it's a meal.
        (9)  Don't feel you must finish everything on your plate.  You
             can always eat it later.
        (10) Avoid any wine with a childproof cap.
        (11) Avoid blue food.
                -- Richard Smit, "The Bronx Diet"

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Raspunde prin e-mail lui