Potential Same Name Bug

2016-09-12 Thread Kevin Smith
I hit an issue in Git today that seemed to be a bug. Basically what happened is in our master branch we had two files, one named something like "file_NAME.png" and another named "file_name.png" in the same folder. In the develop branch in the same repo we had removed the "file_NAME.png" file so t

Re: Last mile to 1.0?

2005-07-23 Thread Kevin Smith
Ryan Anderson wrote: Git falls into the category of distributed source code management tools, similar to Arch or Darcs (or, in the commercial world, BitKeeper). This means that every working directory is a full-fledged repository with full revision tracking capabilities. That's not actually wh

Dumb servers (was: [ANNOUNCE] Cogito-0.12)

2005-07-07 Thread Kevin Smith
Eric W. Biederman wrote: Linus Torvalds <[EMAIL PROTECTED]> writes: That said, I really think the dumb protocols are useless anyway. No other system supports pure static object pulling anyway, and as far as I'm concerned, I want "rsync" to kind of work (but it won't be optimal, since re-pack

Re: [PATCH] git-pasky spec file

2005-04-22 Thread Kevin Smith
Chris Wright wrote: > Here's a simple spec file to do rpm builds. (snip) > Creates a package named git, which seems > fine since Linus' isn't likely to be packaged directly. Um. Really? I can't imagine why Linus's git wouldn't be packaged directly. He has strongly indicated that folks who want

Re: [darcs-devel] Darcs and git: plan of action

2005-04-19 Thread Kevin Smith
Ray Lee wrote: > On Mon, 2005-04-18 at 22:05 -0400, Kevin Smith wrote: > >>Notice that just by looking at my diffs, you can't tell that I used a >>replace operation. > > > Here's where we disagree. If you checkpoint your tree before the > replace, and im

Re: missing: git api, reference, user manual and mission statement

2005-04-19 Thread Kevin Smith
Ingo Molnar wrote: > * Kevin Smith <[EMAIL PROTECTED]> wrote: > >>Git is very immature, and currently should only be used by brave >>pioneers. About the only way for a mortal to even try git is to stick >>to git-pasky releases, and not try to track all the patc

Re: missing: git api, reference, user manual and mission statement

2005-04-19 Thread Kevin Smith
Klaus Robert Suetterlin wrote: > 1) There is no clear (e.g. by name) distinction between ``git as done > by Linus'', which is a kind of content addressable database with added > semantics, and ``git as done by the rest of You'', which is a kind of > SCM on top of Linuses stuff. I also see this as

SCM ideas from 2003

2005-04-18 Thread Kevin Smith
I just stumbled across this page, dated 2003, which foreshadows a couple of the decisions Linus has made for git: http://ydirson.free.fr/en/software/scm/vc.txt Here are the parts that particularly caught my eye: "what's so special about files ?" where the author suggests that existing SCM syst

Re: [darcs-devel] Darcs and git: plan of action

2005-04-18 Thread Kevin Smith
Ray Lee wrote: > On Mon, 2005-04-18 at 21:05 -0400, Kevin Smith wrote: > >>>>The other is "replace very instace of identifier `foo` with >>>>identifier`bar`". >>> >>>That could be derived, however, by a particularly smart parser [1]. >

Re: [darcs-devel] Darcs and git: plan of action

2005-04-18 Thread Kevin Smith
Ray Lee wrote: > On Mon, 2005-04-18 at 21:04 +, [EMAIL PROTECTED] wrote: > >>The other is "replace very instace of identifier `foo` with identifier`bar`". > > > That could be derived, however, by a particularly smart parser [1]. No, it can't. Seriously. A darcs replace patch is encoded as r

Re: Yet another base64 patch

2005-04-18 Thread Kevin Smith
David A. Wheeler wrote: > Does anyone know of any other issues in how git data is stored that > might cause problems for some situations? Windows' case-insensitive/ > case-preserving model for NTFS and vfat32 seems to be enough > (since the case is preserved) so that the format should work, If gi