On Thu, 27 Mar 2008, Andreas Schwab wrote:
>> I've been waiting until I had the time to rewrite my import with proper
>> author names. Does anyone have a correspondence file mapping the login
>> name to Author?
> I have a list that is about 4 months old. Should be pretty complete.
Cute. How abo
On Sun, Aug 17, 2008 at 06:30:57PM +0200, Gerald Pfeifer wrote:
>On Thu, 27 Mar 2008, Andreas Schwab wrote:
>>> I've been waiting until I had the time to rewrite my import with proper
>>> author names. Does anyone have a correspondence file mapping the login
>>> name to Author?
>> I have a list th
Christopher Faylor wrote:
On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote:
Dear GCC devs,
Please do *not* use the full logs of the merged revisions as the
commit message of a merge. Apart from making the output of svn log
useless, commits messages are parsed are tracked f
It's listed on the wiki that explains how to maintain branches :)
On Sun, Aug 17, 2008 at 2:32 PM, John Freeman <[EMAIL PROTECTED]> wrote:
> Christopher Faylor wrote:
>>
>> On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote:
>>
>>>
>>> Dear GCC devs,
>>>
>>> Please do *not* use t
Daniel Berlin wrote:
It's listed on the wiki that explains how to maintain branches :)
I had no idea such a wiki even existed. It would really help future
contributors, I'm sure, if, perhaps during copyright assignment, there
were some sort of "introduction" process that clearly communicat
* Daniel Berlin wrote on Sun, Aug 17, 2008 at 09:18:01PM CEST:
> It's listed on the wiki that explains how to maintain branches :)
It should be on svnwrite.html, or at least a pointer to the wiki
page should be.
Cheers,
Ralf
On Sun, 17 Aug 2008, John Freeman wrote:
> No one informed me of any commit policies when I was given subversion
> access. I thought that since I was working on a branch, I had free
> reign. Education would go a long way in preventing future errors.
You are right. This is one of the weaknesse
On Sun, 17 Aug 2008, Christopher Faylor wrote:
> I don't think adding YA place that has to be updated when things change
> is a good idea. If this is a script that runs on gcc.gnu.org then you
> should be able to get the full name with a minimal amount of effort
> using a getpw* function.
Okay, I
