Re: branches_of_interest.txt - Mailing list pgsql-hackers

From Tom Lane
Subject Re: branches_of_interest.txt
Date
Msg-id 63328.1530536412@sss.pgh.pa.us
Whole thread Raw
In response to Re: branches_of_interest.txt  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
> <andrew.dunstan@2ndquadrant.com> wrote:
>> An alternative would be to create a special branch within the core
>> repo for such data, something like this (The first two lines are the
>> ones that are most important):
>> ...
>> The new branch won't share any history or files with the existing branches.

> Seems like too much magic to me.

Dunno, I was wondering yesterday whether something like that would be
possible.  It'd be easier to maintain than a separate repo, for sure.

I wonder what that would look like in gitweb, though.  If the website
treated it like a version branch, it'd likely be weird.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: branches_of_interest.txt
Next
From: Don Seiler
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" log message