search for: r1234

Chris Lattner <clattner at apple.com> writes: > I completely agree. The "branch" I most care about is mainline, and > losing the ability to say "fixed in r1234" (with some sort of > monotonically increasing number) would be a tragic loss. The monotonically increasing number is useful for giving you a fuzzy idea about how that change relates to other changes wrt the order it was applied and, similarly, the approximate timeline. The usefulness of...

Everybody, When you ask a question, please don''t forget to mention what versions of software you''re running - for example: * OS X 10.4.9 * Ruby 1.8.6 * RSpec 1.8.2 or RSpec trunk r1643 * Spec::Rails 1.8.2 or Spec::Rails tag r1234... * Rails 1.2.3 or Rails edge r5645 * Whatever other relevant software. Because, you see, without this information it''s like solving 1 equation (your question) with 5 unknown variables (the versions). And I think you all know that that is a tough challenge. Please *repeat* this informat...

...so we don't need to resort to timestamps or tags. Mercurial has local revision numbers for this purpose, which I thought were quite handy. Comments on that point are welcome. I completely agree. The "branch" I most care about is mainline, and losing the ability to say "fixed in r1234" (with some sort of monotonically increasing number) would be a tragic loss. -Chris

Greetings; Nut pull & build from about two weeks ago, 2.4.3 I believe. Belkin UPS. I have everything working but a proper shutdown of upsd when I reboot, it hangs there and needs the hdwe reset button to reset it. That may be related to my finding more than 1 K##upsd and more than one K##upsmon, in /etc/rc5.d and which I have now nuked. However, while its working well enough to monitor,

On Jul 22, 2011, at 12:29 AM, Matthieu Moy wrote: > Andrew Trick <atrick at apple.com> writes: > >> SVN revision numbers are central to my workflow. I use them to tag >> results generated against various builds. I like those results sorted >> by time and the chronology should be obvious, > > This means in the presence of branches, you want the ordering to be

Andrew Trick <atrick at apple.com> writes: > SVN revision numbers are central to my workflow. I use them to tag > results generated against various builds. I like those results sorted > by time and the chronology should be obvious, This means in the presence of branches, you want the ordering to be [branch A] build 1 [branch B] build 2 [branch A] build 3 [branch C] build 4 ? It

On 10/16/2019 12:02 PM, Roman Lebedev wrote: > On Wed, Oct 16, 2019 at 9:55 PM Tom Stellard <tstellar at redhat.com> wrote: >> >> On 10/16/2019 07:31 AM, Roman Lebedev wrote: >>> +1, please. >>> >>> Also, putting a tag on the *first* commit in the repo, >>> and doing `git describe --match FIRST_COMMIT_TAG` will be *great*! >>>