All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: c/s 20384
Date: Tue, 03 Nov 2009 11:06:03 -0800	[thread overview]
Message-ID: <4AF07F1B.4090803@goop.org> (raw)
In-Reply-To: <4AF00F6B020000780001D4BA@vpn.id2.novell.com>

On 11/03/09 02:09, Jan Beulich wrote:
> Hmm, I think http://xenbits.xensource.com/xen-unstable.hg can
> reasonably be considered a canonical reference, and hence I would
> assume that using the small number ids is uniquely identifying a c/s.
>   

I have a repo here which is what I'm going to refer to if you highlight
a particular changeset for some reason.  If I have to go back to xenbits
to map a local change number to a changeset id then that's pretty
awkward (particularly if I'm not online at the time).

> Furthermore, using the full ids doesn't allow easily judging how long
> ago the referred to c/s was committed, including immediately knowing
> which releases it may have been part of.
>   

That's pretty easy to determine once you look it up.  I don't know that
I have a good idea about how change numbers relate to releases anyway.

    J

      reply	other threads:[~2009-11-03 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  8:17 c/s 20384 Jan Beulich
2009-11-02  9:40 ` Keir Fraser
2009-11-02 21:08 ` Jeremy Fitzhardinge
2009-11-02 21:39   ` Keir Fraser
2009-11-03 10:09   ` Jan Beulich
2009-11-03 19:06     ` Jeremy Fitzhardinge [this message]

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=4AF07F1B.4090803@goop.org \
    --to=jeremy@goop.org \
    --cc=JBeulich@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.
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.