Hi
I'm starting to write some docs...
Comments... even yep, looks OK, carry on :)
I plan on putting the 'git command' ones into the 'git help ...'
structure once Petr accepts it.
I guess the low level ones go into a README.reference until they
stabilise and become man pages...
In doing this I
On Wed, 20 Apr 2005, David Greaves wrote:
In doing this I noticed a couple of points:
* update-cache won't accept ./file or fred/./file
The comment in update-cache.c reads:
/*
* We fundamentally don't like some paths: we don't want
* dot or dot-dot anywhere, and in fact, we don't even want
*
C. Scott Ananian wrote:
On Wed, 20 Apr 2005, David Greaves wrote:
In doing this I noticed a couple of points:
* update-cache won't accept ./file or fred/./file
The comment in update-cache.c reads:
/*
* We fundamentally don't like some paths: we don't want
* dot or dot-dot anywhere, and in fact,
On Wed, 20 Apr 2005, David Greaves wrote:
So maybe it's left as documented behaviour and higher level tools must
manage the data they feed to it...
That was the plan.
I agree that find . -type f | xargs update-cache --add -- in _theory_ is
a nice thing to do. But in practice, you want to
4 matches
Mail list logo
