On 5/21/2016 6:27 PM, John P. Rouillard wrote:
> In message <3d27b874-c4db-f4e9-956f-7bbfd651b...@gmail.com>,
> Andy Goth writes:
>> How about tags? Put the description in the check-in manifest of the
>> first usage of the tag, I suppose.
>
> That's my thought. IIUC a property with no value is
Hi Andy:
In message <3d27b874-c4db-f4e9-956f-7bbfd651b...@gmail.com>,
Andy Goth writes:
>On 5/21/2016 4:53 PM, John P. Rouillard wrote:
>> In message ,
>> "Tony Papadimitriou" writes:
>>> I've had the same wish for a long long time. I would
>>> like
On 5/21/2016 4:53 PM, John P. Rouillard wrote:
> In message ,
> "Tony Papadimitriou" writes:
>> I've had the same wish for a long long time. I would like the FOSSIL BRANCH
>> list to show except for the branch name some kind of description.
>> Like you
Hi all:
In message ,
"Tony Papadimitriou" writes:
>I've had the same wish for a long long time. I would like the FOSSIL BRANCH
>list to show except for the branch name some kind of description.
>Like you mentioned, making the branch name itself long
if a branch is private. This
would be very helpful to me (at least).
Add another €0.01
-Original Message-
From: Andy Goth
Sent: Saturday, May 21, 2016 5:39 AM
To: Fossil Users Mailing List
Subject: [fossil-users] Branch and tag metadata
I'm thinking I might want the ability to describe
I'm thinking I might want the ability to describe branches and tags
separate from the check-in comments.
Maybe a wiki page with the same name as the branch or tag would serve
the purpose, then in the wiki page there could be links to tickets or
whatever else is needed to describe what is going
6 matches
Mail list logo