From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Tag 9.1rc1. |
Date: | 2011-08-19 14:15:07 |
Message-ID: | CABUevEw-SC6YRkteoUCK8qfjx6gnh1nqzvJp5Kg1SBs7L5rNNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
We seem to have been fairly inconsistent in whether we call this
operation "tag" or "stamp", if we look at it historically. With a
little turn towards "tag" lately.
May I humbly suggest that we actually start calling it "stamp"
instead, to make it very clear that this is a different operation from
the "git tag" operation that's done on the tree a bit later?
Reasonable?
//Magnus
On Thu, Aug 18, 2011 at 23:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Tag 9.1rc1.
>
> Branch
> ------
> REL9_1_STABLE
>
> Details
> -------
> http://git.postgresql.org/pg/commitdiff/d89b8daf5ee05f9c6fa63695e88d2315a224bf2d
>
> Modified Files
> --------------
> configure | 18 +++++++++---------
> configure.in | 2 +-
> doc/bug.template | 2 +-
> src/include/pg_config.h.win32 | 6 +++---
> 4 files changed, 14 insertions(+), 14 deletions(-)
>
>
> --
> Sent via pgsql-committers mailing list (pgsql-committers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-committers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2011-08-19 14:45:44 | Re: pgsql: Tag 9.1rc1. |
Previous Message | Tom Lane | 2011-08-18 21:24:46 | pgsql: Tag 9.1rc1. |