Re: [Issue #3947] fixing \huge et al.

[James]

Kieren,

On Sun, 25 Jun 2017 11:35:37 -0400
Kieren MacMillan <address@hidden> wrote:

> Hi Marc,
> 
> Thanks for the quick response.
> 
> > I think that no response means "yes, submit a patch" in this case.
> > If you checked your changes and did not find any negative effects,
> > then submitting a patch is the best way to go IMHO.  
> 
> Okay.
> 
> > The guidance/mentoring is great in principle, but it is way easier
> > for developers to comment on "official" patches during the review
> > process.  
> 
> Fair enough.
> I'll move forward towards a patch, and ping the list if I git-stumble.
> 
> Thanks,
> Kieren.

I am sure you know the process, but in case, just make sure that there
is a tracker issue AND that the tracker issue is marked as 'started'
with patch 'new' so that it appears on the countdown list for me to
check/test/move etc.

git-cl should do this automatically.

James