On December 14, 2017 1:50:00 PM EST, Junio C Hamano wrote:
>I agree with that. I do not consider the proposed change "good".
Why is "index" better? It is a confusing name, one that has many other
unrelated meanings. In particular, many projects managed by git also have an
index, but few have
On December 13, 2017 7:54:04 AM EST, "Ævar Arnfjörð Bjarmason"
wrote:
>After your patch the majority of the docs will still talk about
>"index", is this part of some larger series, perhaps it would be good
>to see it all at once...
Yes, this would be part of a larger series.
I'm happy to do the
.
If the phrase "staging area" is consistently used *instead* of index,
there's no problem. E.g., "git clean consults the staging area"
conveys exactly the same information as "git clean consults the index"
when index == staging area.
The term "index" has too many *other* meanings.
--- David A. Wheeler
On December 13, 2017 12:40:12 AM EST, Jacob Keller
wrote:
>I know we've used various terms for this concept across a lot of the
>documentation. However, I was under the impression that we most
>explicitly used "index" rather than "staging area".
I think "staging area" is the better term. It focu
ently use
the phrase "staging area", which is higher-level and should be less
confusing for new users.
Signed-off-by: David A. Wheeler
---
Documentation/git-add.txt | 104 --
1 file changed, 54 insertions(+), 50 deletions(-)
diff --git a/Docu
nding git's documentation will make it easier to argue
that developers understood --signoff when they use it.
Signed-off-by: David A. Wheeler
---
Documentation/git-am.txt | 1 +
Documentation/git-cherry-pick.txt | 1 +
Documentation/git-commit.txt | 6 +-
Document
; having it configured via the user/system config might be an
> interesting feature.
Would that be acceptable to the wider group?
--- David A. Wheeler
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majord
censing text might be incomplete, but having that
information
provides a big help, and it's what most people rely on anyway. Indeed, a *lack*
of this is a sign of trouble, which is exactly what warnings are good for.
--- David A. Wheeler
(P.S. I posted this previously but it seems to have fa
er.com/stephenrwalli/status/247597785069789184
Signed-off-by: David A. Wheeler
---
builtin/clone.c | 44
1 file changed, 44 insertions(+)
diff --git a/builtin/clone.c b/builtin/clone.c
index 9572467..a3e8584 100644
--- a/builtin/clone.c
+++ b/builtin/cl
accidentally omit a license, so this is common enough to note.
For more info on the issue, feel free to see:
http://choosealicense.com/no-license/
http://www.wired.com/2013/07/github-licenses/
https://twitter.com/stephenrwalli/status/247597785069789184
Signed-off-by: David A. Wheeler
---
builtin/clone.c
east)
will probably be rewritten in Perl, and anything performance-sensitive
will be in C.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
ests on Fedora Core 3 and OpenBSD.
On Fedora Core 3, I can say that bash, ash & csh all do NOT
consider "#" as a comment start if an alpha precedes it.
The same is true for OpenBSD /bin/sh, /bin/csh, and /bin/rksh.
If such different shells do the same thing (this stuff isn't even
hack I posted earlier, this should be
"clean everywhere" (assuming you have mktemp).
This is a patch against git-pasky 0.6.3.
This is my first attempt to _post_ a patch using git itself,
and I'm not entirely sure how you want it. Let me know
if you have a problem with it!
--- David
PDIR everywhere.
Not a good final solution, but enough to get started in the interim.
In long term, this should be made more portable, but it's
only ~2 weeks old after all. Some people are trying to fly this plane
to transport a buffalo herd, while others are working to attach the
wings :-).
easily.
E.g., if "cg-update" is a Perl script, then you can create a file
"cg-update.bat":
perl \path\to\cg-update %*
(That requires Windows NT4 or better. MS-DOS didn't have %*, so you needed:
perl \path\to\cg-update %1 %2 %3 %4 %5 %6 %7 %8 %9
It's hard to imagine
Forget my earlier "aspatch" proposal, that's a lousy name.
How about "mkpatch"? Seems like a reasonable name for
a command that makes a patch. GNU Arch uses that command name.
CVS & Subversion basically do this as part of "diff"
(which is another
something else
(good names, anyone?).
Good externally-viewed names are critical... good
command names that are similar to what people "already know"
can really help make the tool a joy to use.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
use you want to do things in stages).
The commands "update" and "pull" come to mind when thinking that way,
though as long as the commands are simple & clear that's a good thing
(I think it's a GOOD idea to use the same commands as CVS and
Subversion when the results
do that right now; the shell is an excellent prototyping tool.
But once things have settled down & there's been some experience
with the tools, the pieces could be slowly recoded.
(Yes, I know of & use Cygwin. And I prefer Python over Perl,
but I'm really uninterested in language
update" as meaning this (auto download & merge from the
given repository), so the terminology would make sense for some.
I'd be happy to send in a patch to do that. The coding is trivial,
but it means a UI change in one of the most common commands
(use "update" instead of &qu
target, but when there are opportunities to make
> the data structures more generally useful without causing problems for
> the kernel project, I hope they are taken.
Thanks for the vote of confidence!
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
gets into the mainline,
and 3 commits before the final mainline patch, I get
approximately this many objects in a "real" object db:
(28237*(3+1) trees) *2 (if #commits==#trees) +
(188119*(5+1) file objs))
= 1,354,610 objects from 2002/02/05 to 2005/04/04
= about 36,000 objects/month.
Am I missing anything?
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
g for more generalized solutions, where
non-English comments are more common than in Linux kernel code.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
easy to set most editors up to read & write UTF-8.
Having the data stored as a constant charset eliminates
a raft of error-prone code.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
tion would be of
particular help to other projects. I'm more worried about the
storage format; if the code doesn't support some particular
feature but it could be added later without great pain, no big deal.
If something would imply a complete rewrite, that's undesirable.
--- David A.
H^H^H^H^H developers who come later.
Yes, a tool can handle the conversion, but choosing formats
so a tool is unneeded for simple stuff is often better!
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
M
format, because they'll be serving
objects by URL, not by sha1.
If the "layout info" is stored in a standard location for a
given repository, then the rest doesn't matter. The library would just
download that, then know how to find the rest.
--- David A. Wheeler
-
To unsubscribe
Linus Torvalds wrote:
On Sun, 17 Apr 2005, David A. Wheeler wrote:
There's a minor reason to write out ALL the perm bit data, but
only care about a few bits coming back in: Some people use
SCM systems as a generalized backup system
Yes. I was actually thinking about having system config files
andle the number of objects in those cases?
If it works, your infrastructure should be sufficiently
portable to "just work" on others too.
Anyway, my two cents.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message
ux, xattrs, whatever. For some, that's enough.
Yeah, I know, not the main purpose of git. But what the heck,
I _like_ flexible infrastructures.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Paul Jackson wrote:
Junio wrote:
Sounds like svn
I have no idea what svn is.
svn = common abbreviation for "Subversion", a
widely-used centralized SCM tool intentionally
similar to CVS.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
t
could later on CONFIRM with much more certainty who
REALLY submitted a given change... say if it was clearly malicious).
If you switch hash algorithms, the signatures might not work,
depending on how you do it.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
any have undergone radical and
painful surgeries so that they can be more portable to
various filesystems.
It's a trade-off, I know.
--- David A. Wheeler
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
33 matches
Mail list logo
