[RFC] warn people about the permanence of branches
timeless
timeless at gmail.com
Tue Dec 6 04:42:16 UTC 2011
I'd go with "no active branches in the last year". -- and yes, I know
that date stamps are fungible.
Old migrated or closed branches could date to a previous policy.
Mozilla of late has reminded me that projects have policy and people
churn and tend to forget previous decisions.
On 12/5/11, Augie Fackler <durin42 at gmail.com> wrote:
> On Dec 5, 2011, at 5:22 PM, Matt Mackall wrote:
>>
>> Looks like our efforts to alert people exposed to Git to the permanence
>> of branches in non-Git systems need help. I propose:
>>
>> diff -r 09b200396384 mercurial/commands.py
>> --- a/mercurial/commands.py Mon Dec 05 17:09:11 2011 -0600
>> +++ b/mercurial/commands.py Mon Dec 05 17:12:10 2011 -0600
>> @@ -855,6 +855,8 @@
>> hint=_("use 'hg update' to switch to
>> it"))
>> repo.dirstate.setbranch(label)
>> ui.status(_('marked working directory as branch %s\n') % label)
>> + ui.warn(_('warning: branches are permanent and global,'
>> + ' did you want a bookmark?\n'))
>
> Perhaps we could be smarter about this and only do it if branches other than
> default don't already exist in the repo?
>
> I'm not sure I'm convinced one way or the other if that'd be sufficient.
>
>> else:
>> ui.write("%s\n" % repo.dirstate.branch())
>
>
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
--
Sent from my mobile device
More information about the Mercurial-devel
mailing list