[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[patches] Git repository
- To: patches@xxxxxxxxxx
- Subject: [patches] Git repository
- From: Heikki Orsila <shd@xxxxxxxxxx>
- Date: Fri, 8 May 2009 12:18:59 +0300
I was very pleased to hear that eglibc project exists. I have two
issues / suggestions:
1. Would you accept strlcpy()/strlcat() functions into eglibc?
http://www.rocketaware.com/man/man3/strlcpy.3.htm
strncpy is slow: it pads the whole destination buffer with nulls. Often
this leads to multiple useless memory accesses as the destination buffer
is much larger than the source buffer.
strncpy is hard: one often puts an extra null byte to the end of the
destination buffer and calls strlen() several times.
2. Have you considered switching from SVN to Git? Git would improve
some operations:
* Tracks patch _authors_ and _committers_ separately
* chain of trust gets recorded
* authors get credited through the SCM tool
* Lower threshold for 3rd party contributions: Git provides
good tools to contribute formatted patches, including change
log entries, timestamps etc.
* Better log inspection tools
* more versatile tools (such as bisection, branching and merging
tools)
Git is currently used by Linux, Perl, Gnome, X.org, Ruby on Rails,
Fedora, ...
--
Heikki Orsila
heikki.orsila@xxxxxx
http://www.iki.fi/shd