From: Ben Guthro <bguthro@virtualiron.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: API Changelog
Date: Mon, 07 Jan 2008 11:30:28 -0500 [thread overview]
Message-ID: <478253A4.20707@virtualiron.com> (raw)
In-Reply-To: <20080107162233.GA19323@totally.trollied.org.uk>
It does via an extension:
http://www.selenic.com/mercurial/wiki/index.cgi/KeywordExpansionExtension
http://osdir.com/ml/os.solaris.opensolaris.tools.general/2006-05/msg00167.html
John Levon wrote:
> Now I remember why I didn't want a file in the source tree. There's
> absolutely no sensible way to have any entries there that give a
> meaningful link to the actual details - you can't link to the rev until
> it's merged, and you can't commit until the rev is written in it.
>
> The only other option is dates which is way too vague (date when the
> patch was written is a really poor indicator of when the change got
> merged).
>
> I guess keywords would help, except mercurial doesn't do them. Keir?
>
> regards
> john
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2008-01-07 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 16:22 API Changelog John Levon
2008-01-07 16:30 ` Ben Guthro [this message]
2008-01-07 17:12 ` John Levon
2008-01-07 16:34 ` API Changelog [new functionality] Stefan de Konink
2008-01-08 16:54 ` Ian Jackson
2008-01-08 16:56 ` Ian Jackson
2008-01-08 16:58 ` Keir Fraser
2008-01-08 17:10 ` Stefan de Konink
2008-01-07 17:47 ` API Changelog Keir Fraser
2008-01-08 0:32 ` Mark Williamson
2008-01-08 16:46 ` Ian Jackson
2008-01-08 18:28 ` Mark Williamson
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=478253A4.20707@virtualiron.com \
--to=bguthro@virtualiron.com \
--cc=levon@movementarian.org \
--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.